Help deciphering a crash report

General
1

Hi there,
I’ve got someone who’s getting hard crashes; the crash report is beyond me, though. Can anyone help shed any light?
Thanks,
Hamish

[code]Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000e585044
Exception Note: EXC_CORPSE_NOTIFY

VM Regions Near 0xe585044:
VM_ALLOCATE 000000000e57c000-000000000e57e000 [ 8K] rw-/rwx SM=PRV
–>
CG shared images 000000000e5a1000-000000000e5a9000 [ 32K] r–/r-- SM=PRV

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x9df8187d CFRelease + 29
1 com.apple.CoreFoundation 0x9dfb817c -[__NSDictionaryM dealloc] + 188
2 libobjc.A.dylib 0x9122adbd objc_object::sidetable_release(bool) + 239
3 libobjc.A.dylib 0x9122c1e6 -[NSObject release] + 25
4 com.apple.CoreFoundation 0x9df81c57 CFRelease + 1015
5 com.apple.CoreFoundation 0x9dfa28f5 __CFTypeCollectionRelease + 165
6 com.apple.CoreFoundation 0x9df9399e __CFBasicHashDrain + 510
7 com.apple.CoreFoundation 0x9df93774 __CFBasicHashDeallocate + 52
8 com.apple.CoreFoundation 0x9df81b5e CFRelease + 766
9 com.apple.print.framework.PrintCore 0x9ded62de OpaquePMPrintSession::~OpaquePMPrintSession() + 204
10 com.apple.print.framework.PrintCore 0x9ded61f3 OpaquePMPrintSession::~OpaquePMPrintSession() + 19
11 com.apple.print.framework.PrintCore 0x9decb031 PMBaseObject::Release(PMBaseObject*) + 35
12 com.apple.print.framework.PrintCore 0x9decaff4 PMRelease + 41
13 com.apple.AppKit 0x9d4ed72b -[NSPrintInfo dealloc] + 175
14 libobjc.A.dylib 0x9122adbd objc_object::sidetable_release(bool) + 239
15 libobjc.A.dylib 0x9122c1e6 -[NSObject release] + 25
16 com.apple.AppKit 0x9d4ebfd8 -[NSPrintPanel dealloc] + 59
17 libobjc.A.dylib 0x9122adbd objc_object::sidetable_release(bool) + 239
18 libobjc.A.dylib 0x9122c1e6 -[NSObject release] + 25
19 libobjc.A.dylib 0x91229b10 (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 488
20 com.apple.CoreFoundation 0x9dfa3b7f _CFAutoreleasePoolPop + 47
21 com.apple.Foundation 0x9a4ba1ec -[NSAutoreleasePool drain] + 122
22 com.apple.AppKit 0x9d2720ba -[NSApplication run] + 946
23 com.xojo.XojoFramework 0x031e22b7 0x3088000 + 1417911
24 com.xojo.XojoFramework 0x031e084c RuntimeRun + 49
25 com.lightbluesoftware.lightblue 0x001f5aed REALbasic._RuntimeRun + 34
26 com.lightbluesoftware.lightblue 0x0000b71e _Main + 257
27 com.lightbluesoftware.lightblue 0x00002738 main + 36
28 com.lightbluesoftware.lightblue 0x02a219b5 start + 53[/code]

2

I’m not a total expert either. But some things stand out:

EXC_CORPSE_NOTIFY: you are talking to something that isn’t there.
You got problems with releasing memory for a NSDictionary while printing.

Can you post the full crash log?

3

It looks like you’re trying to release an object that isn’t there, i.e., has already been released or never existed.

4

[quote=261581:@Hamish Symington]19 libobjc.A.dylib 0x91229b10 (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 488
20 com.apple.CoreFoundation 0x9dfa3b7f _CFAutoreleasePoolPop + 47
21 com.apple.Foundation 0x9a4ba1ec -[NSAutoreleasePool drain] + 122[/quote]
Suggests to me that the OS is releasing an object that you may have already released, make sure your declares do not specify autoRelease on a object and then a release later.

5

The crash report for Thread 0 stops after line 28; would the rest of the report be helpful?
The program seems to crash after finishing a method (i.e. after End Sub) so I think it’s the framework or a plugin letting something go rather than me.

7

I’m using a PrinterSetup, which I’m initialising with a setupstring from a file, and OpenPrinterDialog, initialised with that printersetup. I’m drawing to that using DrawPicture.

For some reason, this quit is only happening on one person’s machine, and it’s not happening every time.

8

submit a bug report with the full crash log attached

The names of entry points may not be correct
We strip symbols from frameworks to make life more difficult for hackers & folks who like to reverse engineer the frameworks so you have limited ability to actually look at a crash and be correct about what its saying