[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class

2010-12-21 Thread nicola at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18764 Nicola Pero changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class

2010-12-21 Thread nicola at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18764 --- Comment #8 from Nicola Pero 2010-12-21 22:49:44 UTC --- Author: nicola Date: Tue Dec 21 22:49:37 2010 New Revision: 168139 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168139 Log: In libobjc/: 2010-12-21 Nicola Pero PR libob

[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class

2006-01-17 Thread pinskia at gcc dot gnu dot org
--- Comment #7 from pinskia at gcc dot gnu dot org 2006-01-17 16:49 --- I don't have time for this bug at least right now. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added --

[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class

2005-09-15 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-16 04:26 --- Actually my testcase works with the next runtime also but that might be because it is picking the first Foo and the one in 2.so. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18764

[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class

2005-09-15 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-16 04:24 --- I am going to implement the next runtime behavior. The following code works and is just like the code in your testcase too but works with both runtimes:) : #include #include #include #ifdef __NEXT_RUN

[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class

2005-09-15 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-16 03:55 --- The next runtime does: objc: Both ./1.so and ./2.so have implementations of class Foo. objc: Using implementation from ./2.so. What do you think we should do, use the later one of the first or abort? --

[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class

2005-09-15 Thread pinskia 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) a

[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class

2004-12-02 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-02 13:37 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW E

[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class

2004-12-01 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added CC||pinskia at gcc dot gnu dot ||org Summary|segfault in

[Bug libobjc/18764] segfault in libobjc when sending a message to a conflicting class

2004-12-01 Thread ratmice at yahoo dot com
--- Additional Comments From ratmice at yahoo dot com 2004-12-01 19:23 --- Created an attachment (id=7652) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=7652&action=view) testcase -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18764