Hi,
Wolfgang Lux wrote:
Instead of speculating I would suggest getting definitive information by
setting a breakpoint at the point where the missing autorelease pool is
reported (line 368 in NSAutoreleasePool.m in the current svn version) and get a
backtrace from gdb.:-)
It is an issue that happens during building!
This is the trace I get:
(gdb) bt
#0 +[NSAutoreleasePool addObject:] (
self=0xbb6c7f80 <_OBJC_Class_NSAutoreleasePool>,
_cmd=0xbb6fd4d8 <_OBJC_SELECTOR_TABLE+120>, anObj=0x8f57650)
at NSAutoreleasePool.m:368
#1 0xbb4442c9 in -[NSObject autorelease] (self=0x8f57650,
_cmd=0xbb6f6440 <_OBJC_SELECTOR_TABLE+32>) at NSObject.m:1633
#2 0xbb43051f in +[NSMethodSignature signatureWithObjCTypes:] (
self=0xbb6f64c0 <_OBJC_Class_NSMethodSignature>,
_cmd=0xbb7407a0 <_OBJC_SELECTOR_TABLE>,
t=0x843790c <_OBJC_METH_VAR_TYPE_11> "@8@0:4") at
NSMethodSignature.m:559
#3 0xbb515add in gs_objc_msg_forward2 (
receiver=0xbb6c7f80 <_OBJC_Class_NSAutoreleasePool>,
sel=0x843a130 <_OBJC_SELECTOR_TABLE+1008>) at GSFFIInvocation.m:140
#4 0xbb27a8d1 in __objc_get_forward_imp () from /usr/lib/libobjc.so.4
#5 0xbb27c0d2 in objc_msg_lookup () from /usr/lib/libobjc.so.4
#6 0x081e3546 in ns_alloc_autorelease_pool () at nsterm.m:642
#7 0x08218a20 in main (argc=<optimized out>, argv=0xbfbfea5c) at
emacs.c:1213
a bit of context shows... that it is the allocation of the ARP itself!
641 {
642 return [[NSAutoreleasePool alloc] init];
643 }
644
Riccardo
_______________________________________________
Discuss-gnustep mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnustep
