El jue, 24-01-2013 a las 09:59 +0100, Fred Kiefer escribió:
> >
> > Last time I test it, worked perfectly. So maybe this is a bug on
> > GNUstep.
>
> In GNUstep from SVN the line in NSBox this is pointing to gets the size
> from the theme. The segmentation fault there could happen if theme is
>
On 24 Jan 2013, at 10:12, Marcus Müller wrote:
> Hi David,
>
>> A crash in objc_msgSend() usually means that the object that is being sent a
>> message is an invalid pointer. Try enabling zombies and see if it reports
>> an object being deallocated.
>
> that's clear - but why can't I print i
Hi David,
> A crash in objc_msgSend() usually means that the object that is being sent a
> message is an invalid pointer. Try enabling zombies and see if it reports an
> object being deallocated.
that's clear - but why can't I print it in gdb? I just want to inspect the
pointer, but even that
Hi Marcus,
A crash in objc_msgSend() usually means that the object that is being sent a
message is an invalid pointer. Try enabling zombies and see if it reports an
object being deallocated.
David
P.S. On FreeBSD, it's usually best to use gdb from ports, as the one in base
doesn't understand
Hi,
I'm hunting a bug in conjunction with GSAvahiNetService. I'm on FreeBSD 9.1
with clang 3.1 and current libobjc2 and GNUstep (both svn r36011).
The stacktrace is as follows:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 806c07400 (LWP 100877)]
0x0008011d23ac i
On 24.01.2013 07:11, Germán A. Arias wrote:
Currently Cenon 3.9.6 crash at launch with GNUstep from SVN. Here the
backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x00a84294 in objc_msg_lookup ()
from /usr/lib/i386-linux-gnu/libobjc.so.3
(gdb) backtrace
#0 0x00a84294 in objc_msg_
