Thinking ahead on debugging....

Post Reply
donaldquixote
Posts: 3
Joined: Sat Sep 13, 2008 5:39 am

Thinking ahead on debugging....

Post by donaldquixote » Wed Aug 26, 2009 10:27 pm

Hi all,

I'm beginning work on my second DS project. This time through, I am hoping to avoid some of the debug headaches I ran into the first time, so I've been looking into methods for gathering data on crashes/hangs.

Anyway, I have two questions:
First, I'm using the default exception handler, and am successfully getting a guru meditation screen on crash. However, it always gives 0x0 as the address, which I know isn't valid. Is there a known cause for this?

Second, are there any other nifty techniques for getting more information on crash? I don't have the full version of nocash, and it seems like I never will. Also, I can print error codes with my asserts to debug console, but you can only use so many asserts. : )

Any help is greatly appreciated!

User avatar
vuurrobin
Posts: 219
Joined: Fri Jul 11, 2008 8:49 pm
Location: The Netherlands
Contact:

Re: Thinking ahead on debugging....

Post by vuurrobin » Wed Aug 26, 2009 10:43 pm

using asserts like hell is probably a good idea. other than that, you could try this out:

http://forums.devkitpro.org/viewtopic.php?f=2&t=1465

you could try to search for emulators that support more debugging stuff than the freeware version of no$gba.

donaldquixote
Posts: 3
Joined: Sat Sep 13, 2008 5:39 am

Re: Thinking ahead on debugging....

Post by donaldquixote » Sat Aug 29, 2009 5:47 am

Thanks for the tip : )

WinterMute
Site Admin
Posts: 1986
Joined: Tue Aug 09, 2005 3:21 am
Location: UK
Contact:

Re: Thinking ahead on debugging....

Post by WinterMute » Thu Sep 03, 2009 2:01 am

Which address is always 0x0? If it's the access address then that's why you get the exception ...
Help keep devkitPro toolchains free, Donate today

Personal Blog

Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot] and 2 guests