[Top][All Lists]

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

Re: Seg fault in GSIMapCleanMap in gnustep-base-1.24.8

From: David Chisnall
Subject: Re: Seg fault in GSIMapCleanMap in gnustep-base-1.24.8
Date: Thu, 30 Jul 2015 10:10:28 +0100

On 29 Jul 2015, at 16:47, David Lobron <address@hidden> wrote:
> #0  0xf73fc056 in objc_msg_lookup () from /usr/lib32/libobjc.so.3
> #1  0xf749e290 in GSIMapCleanMap (map=0x818efb4) at 
> ../Headers/GNUstepBase/GSIMap.h:1188
> #2  GSIMapCleanMap (map=0x818efb4) at GSDictionary.m:117
> #3  GSIMapEmptyMap (map=0x818efb4) at ../Headers/GNUstepBase/GSIMap.h:1219
> #4  -[GSDictionary dealloc] (self=0x818efb0, _cmd=0xf783c5f0) at 
> GSDictionary.m:118
> #5  0xf75c0395 in -[NSObject release] (self=0x818efb0, _cmd=0xf7f84528) at 
> NSObject.m:2105
> #6  0xf7c28290 in -[Configuration dealloc] (self=0x819ed18, _cmd=0xf7f7d7a0) 
> at Configuration.m:715
> The code that triggers the error is in my dealloc method - I'm calling 
> "release" on an NSDictionary object.  The crash doesn't happen every time 
> under gdb, but it does occur reliably outside gdb.

This looks like it’s trying to release an object that’s already been destroyed. 
 What happens if you run the program with valgrind or NSZombie?


-- Sent from my Apple II

reply via email to

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