This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Odd problem with libobjc
On dom, 2011-07-24 at 18:59 +0100, Nicola Pero wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0xb523b6c0 (LWP 24619)]
> > 0xb6e00fe6 in objc_msg_lookup (receiver=0x85b1988, op=0xb7211da0)
> > at /home/german/Instalados/GCC/gcc-4.6.0/libobjc/sendmsg.c:397
> > 397 /home/german/Instalados/GCC/gcc-4.6.0/libobjc/sendmsg.c: No such
> > file or directory.
> > in /home/german/Instalados/GCC/gcc-4.6.0/libobjc/sendmsg.c
> > Current language: auto; currently c
>
> [...]
>
> > home/german/Instalados/GCC was the path where I extracted the GCC
> > tarball, when I install it (GCC 4.6.0). The GCC folder don't exist
> > anymore. So I suppose this is a bad configuration problem. I have
> > installed GCC at /usr/local/bin/gcc, but why it search files at my home
> > directory? Any advice to solve this? Thanks.
>
> The segmentation fault is most likely caused by trying to send a message
> to an object which has already been deallocated. In other words, it is most
> likely a bug in the program (check retain/release logic etc), not in libobjc.
> It is not a configuration problem. ;-)
>
> The mention of no longer existing source files in the error messages or in gdb
> most likely doesn't have much to do with the cause of the segmentation fault. It's
> just trying to tell you where the crash occurred. If you have deleted the source files,
> they no longer exist, but that should not be a particular problem. :-)
>
> Thanks
I will try with Valgrind as suggested David in gnustep mail list. But
after the last update I do in gnustep, almost all apps crash :(
Thanks.