Two crashes

For test results, bug reports, announcements of new builds etc.

Moderators: winston, another_commander, Getafix

Post Reply
User avatar
Commander McLane
---- E L I T E ----
---- E L I T E ----
Posts: 9520
Joined: Thu Dec 14, 2006 9:08 am
Location: a Hacker Outpost in a moderately remote area
Contact:

Two crashes

Post by Commander McLane »

I got two crashes during the weekend, while playtesting a revised Tianve.oxp. No idea whether they are related to what I'm doing there (I am mainly overhauling AIs). Nothing at all in the game log, except that I had enabled AI logging, and got the repetetive usual messages every ten seconds during a long flight to a distant destination. And at some random point in-between the game crashed unexplicably.

Here are the relevant parts of the crash logs:

Code: Select all

Date/Time:      2009-11-28 23:39:01.248 +0300
OS Version:     10.4.11 (Build 8S2167)
Report Version: 4

Command: Oolite
Path:    /Applications/Spiele/Oolite 1.73.4/Oolite.app/Contents/MacOS/Oolite
Parent:  WindowServer [55]

Version: Oolite version 1.73.4 (1.73.4)

PID:    3786
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x3866633f

Thread 0 Crashed:
0   libobjc.A.dylib                	0x90a59387 objc_msgSend + 23
1   org.aegidian.oolite            	0x0000982c -[AI takeAction:] + 404
2   org.aegidian.oolite            	0x000095f1 -[AI reactToMessage:] + 705
3   org.aegidian.oolite            	0x00009881 -[AI takeAction:] + 489
4   org.aegidian.oolite            	0x000095f1 -[AI reactToMessage:] + 705
5   org.aegidian.oolite            	0x00009acf -[AI think] + 211
6   org.aegidian.oolite            	0x00042190 -[Universe update:] + 3029
7   org.aegidian.oolite            	0x0000f5bb -[GameController doPerformGameTick] + 142
8   com.apple.Foundation           	0x92840cca __NSFireTimer + 199
9   com.apple.CoreFoundation       	0x9082d756 CFRunLoopRunSpecific + 3341
10  com.apple.CoreFoundation       	0x9082ca42 CFRunLoopRunInMode + 61
11  com.apple.HIToolbox            	0x92df9878 RunCurrentEventLoopInMode + 285
12  com.apple.HIToolbox            	0x92df8f82 ReceiveNextEventCommon + 385
13  com.apple.HIToolbox            	0x92df8dd9 BlockUntilNextEventMatchingListInMode + 81
14  com.apple.AppKit               	0x9327ef45 _DPSNextEvent + 572
15  com.apple.AppKit               	0x9327eb37 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
16  com.apple.AppKit               	0x932788c4 -[NSApplication run] + 512
17  com.apple.AppKit               	0x9326c820 NSApplicationMain + 573
18  org.aegidian.oolite            	0x00002a62 _start + 216
19  org.aegidian.oolite            	0x00002989 start + 41

Code: Select all

Date/Time:      2009-11-29 17:06:10.910 +0300
OS Version:     10.4.11 (Build 8S2167)
Report Version: 4

Command: Oolite
Path:    /Applications/Spiele/Oolite 1.73.4/Oolite.app/Contents/MacOS/Oolite
Parent:  WindowServer [55]

Version: Oolite version 1.73.4 (1.73.4)

PID:    3822
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x000001a5

Thread 0 Crashed:
0   libobjc.A.dylib                	0x90a59387 objc_msgSend + 23
1   com.apple.Foundation           	0x92840cf2 __NSFireTimer + 239
2   com.apple.CoreFoundation       	0x9082d756 CFRunLoopRunSpecific + 3341
3   com.apple.CoreFoundation       	0x9082ca42 CFRunLoopRunInMode + 61
4   com.apple.HIToolbox            	0x92df9878 RunCurrentEventLoopInMode + 285
5   com.apple.HIToolbox            	0x92df8f82 ReceiveNextEventCommon + 385
6   com.apple.HIToolbox            	0x92df8dd9 BlockUntilNextEventMatchingListInMode + 81
7   com.apple.AppKit               	0x9327ef45 _DPSNextEvent + 572
8   com.apple.AppKit               	0x9327eb37 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
9   com.apple.AppKit               	0x932788c4 -[NSApplication run] + 512
10  com.apple.AppKit               	0x9326c820 NSApplicationMain + 573
11  org.aegidian.oolite            	0x00002a62 _start + 216
12  org.aegidian.oolite            	0x00002989 start + 41
I notice that the "0" in both cases is the same, but that is as much as I understand. Hope that someone with a better grip on the code knows what's going on.
Post Reply