bug-report

hi,
darwinia crashed three times on me (still counting) in the yard-level. it always had something to do with the armour. maybe the armour collision detection?!?!? well whatever here´s my blackbox.txt from the last crash:

=========================
DARWINIA BLACK BOX REPORT

VERSION : macosx-full-1.1.0
ERROR : 'Fatal Signal (10) Received
'

=========================
====== STACKTRACE =======

retAddress = 0x6dbc4
retAddress = 0x6dcc8
retAddress = 0x6da10
retAddress = 0x6d730
retAddress = 0x90025048
retAddress = 0x142384
retAddress = 0x8763c
retAddress = 0x0

maybe you can fix it!
thx felix
btw: it´s a really great game (when it´s not crashing

You need to put it between ( code ) and ( /code ) without the spaces inside the brackets.

This post has been edited by Michael B : 10 April 2005 - 03:34 PM

Actually, there's not a need to enclose it in the code brackets. You can if you want to, but it's easy enough to see the start and end of the reports.

I'll send a message to the list about all these armour problems.

Andcarne, on Apr 12 2005, 12:02 AM, said:

Actually, there's not a need to enclose it in the code brackets. You can if you want to, but it's easy enough to see the start and end of the reports.

I'll send a message to the list about all these armour problems.
View Post

You mean that all the info needed is in the return addresses on the stack? oo-er...

Yeah, it gives references to what was going on at the time of the crash.

Agent_Vast, on Apr 12 2005, 04:34 PM, said:

Yeah, it gives references to what was going on at the time of the crash.
View Post

I know it tells what function was running at the time, but I'd have thought the full info would've been helpful. Debugging a function without knowing what you're looking for must be hard. :S

The Introversion boys have a tool to lookup the stacktrace.