Re: GNUMail crash

[Richard Frith-Macdonald]

On 29 Apr 2015, at 07:08, Riccardo Mottola <riccardo.mottola@libero.it> wrote:
> 
> Hi,
> 
> I just left GNUMail open on my mac and I got it crash with the report below 
> (the crash reporter).
> Does it give any clue to wehere the problem happens in GNUMail?
> I don't get smart from it.
> 
> Riccardo
> 
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
> 
> Thread 0 Crashed:
> 0   <<00000000>>      0xfffeff20 objc_msgSend_rtp + 32
> 1   com.apple.Foundation              0x92be0384 +[NSConcreteNotification 
> newTempNotificationWithName:object:userInfo:] + 300
> 2   com.apple.Foundation              0x92be0204 -[NSNotificationCenter 
> postNotificationName:object:userInfo:] + 60
> 3   ...llaboration-world.Pantomime    0x1002738c -[CWService(Private) 
> _connectionTick:] + 164
> 4   com.apple.Foundation              0x92bf92a0 __NSFireTimer + 116
> 5   com.apple.CoreFoundation          0x907f2384 __CFRunLoopDoTimer + 184
> 6   com.apple.CoreFoundation          0x907decfc __CFRunLoopRun + 1680
> 7   com.apple.CoreFoundation          0x907de2b0 CFRunLoopRunSpecific + 268
> 8   com.apple.HIToolbox               0x932bcb20 RunCurrentEventLoopInMode + 
> 264
> 9   com.apple.HIToolbox               0x932bc1b4 ReceiveNextEventCommon + 380
> 10  com.apple.HIToolbox               0x932bc020 
> BlockUntilNextEventMatchingListInMode + 96
> 11  com.apple.AppKit                  0x937e9734 _DPSNextEvent + 384
> 12  com.apple.AppKit                  0x937e93f8 -[NSApplication 
> nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
> 13  com.apple.AppKit                  0x937e593c -[NSApplication run] + 472
> 14  com.apple.AppKit                  0x938d6458 NSApplicationMain + 452
> 15  ...collaboration-world.GNUMail    0x00002dc8 main + 316
> 16  ...collaboration-world.GNUMail    0x00002c10 _start + 760
> 17  ...collaboration-world.GNUMail    0x00002914 start + 48

Pantomime  ... in CWService _connectionTick seems likely as your problem (or 
whatrewver set up the timer to call it).
The code there seems to be attempting to post a notification, and that's 
crashing ... which suggests that one of the arguments to 
postNotificationName:object:userInfo: is bad (eg a pointer to an object which 
has been deallocated).