emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NeXTstep (GNUstep/Cocoa) port and merging


From: İsmail Dönmez
Subject: Re: NeXTstep (GNUstep/Cocoa) port and merging
Date: Sun, 8 Jun 2008 15:25:33 +0300

Hi,

On Sun, Jun 8, 2008 at 3:18 PM, Thomas Christensen
<address@hidden> wrote:
> "İsmail Dönmez" <address@hidden> writes:
>
>>>  bootstrap-emacs: 
>>> /scratch/packages/gcc/4.3/gcc-4.3-4.3.0/src/libobjc/sendmsg.c:321: 
>>> __objc_init_install_dtable: Assertion 
>>> `(((Class)receiver)&&(((((Class)receiver)->info)&0x1L)==0x1L))' failed.
>>
>> Thats a gcc bug please report it to Debian and/or GCC bugzilla.
>
> Before I do, I tried to compile with gcc-4.2 as well.  Same libobjc2
> though.
>
> I get:
>
> 2008-06-08 14:08:47.633 bootstrap-emacs[9767] autorelease called without pool 
> for object (99ab1c8) of class NSMethodSignature in thread <NSThread: 
> 0x9997438>
> 2008-06-08 14:08:47.660 bootstrap-emacs[9767] autorelease called without pool 
> for object (9a007c8) of class GSAutoreleasedMemory in thread <NSThread: 
> 0x9997438>
> 2008-06-08 14:08:47.660 bootstrap-emacs[9767] autorelease called without pool 
> for object (99aba08) of class NSMethodSignature in thread <NSThread: 
> 0x9997438>
> 2008-06-08 14:08:47.660 bootstrap-emacs[9767] autorelease called without pool 
> for object (99e5580) of class GSFFIInvocation in thread <NSThread: 0x9997438>
> 2008-06-08 14:08:47.661 bootstrap-emacs[9767] autorelease called without pool 
> for object (99db268) of class GSCInlineString in thread <NSThread: 0x9997438>
> 2008-06-08 14:08:47.661 bootstrap-emacs[9767] autorelease called without pool 
> for object (99effb8) of class NSException in thread <NSThread: 0x9997438>
> 2008-06-08 14:08:47.661 bootstrap-emacs[9767] autorelease called without pool 
> for object (99eff68) of class GSMutableArray in thread <NSThread: 0x9997438>
> ../src/bootstrap-emacs: Uncaught exception NSInvalidArgumentException, 
> reason: NSAutoreleasePool(class) does not recognize (null)
>
> So the assertion of 4.3 may be a bug; but something else is afoot too I
> think.

This indeed looks like another issue.

> If you still think it will be good to notify Debian or GCC I will.

GCC 4.3 bug still stands though, its a good idea to report it.

Regards,
ismail

-- 
Never learn by your mistakes, if you do you may never dare to try again.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]