This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Sep 2005 03:54:01 -0000
- Subject: [Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class
- References: <20041201192215.18764.ratmice@yahoo.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-16 03:54 -------
Here is the "real" backtrace:
#0 0x00064374 in sarray_lazy_copy (oarr=0x0) at /Users/pinskia/src/libobjc/gcc/libobjc/sarray.c:484
#1 0x000668d0 in __objc_install_dispatch_table_for_class (class=0x31034) at /Users/pinskia/src/
libobjc/gcc/libobjc/sendmsg.c:430
#2 0x00066454 in __objc_init_install_dtable (receiver=0x31000, op=0x3018) at /Users/pinskia/src/
libobjc/gcc/libobjc/sendmsg.c:314
#3 0x00065f38 in objc_msg_lookup (receiver=0x31000, op=0x3018) at /Users/pinskia/src/libobjc/
gcc/libobjc/sendmsg.c:222
I am deciding if we should cause an internal error if we load two conflicting classes.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18764