Re: [hatari-devel] Exception debugging?

[ Thread Index | Date Index | More Archives ]

Le 06/11/2012 09:38, Eero Tamminen a écrit :
Best would be to have some internal Hatari bitmask variable which
controls which exceptions invoke the debugger.  By default it would
be zero, and -D option would change the mask to catch the above

I could then add --exceptions option to specify a list of
exceptions that should invoke debugger; either as hex, or as
a list of exception numbers or names (similarly to --trace),
whichever way people here on the list prefer.

Or if catching all of above is too much work, at least catching
exceptions 2-8 would be great (then int suffices as bitmask
instead of long long).

	- Eero


as Thomas said, I agree it doesn't make sense to catch all exceptions and go to debugUI, even if debugger is ON.

For example try running the "Transbeauce Demo II" with debugger on and dropping to debugger on exceptions, and you will see it's unusable.

Also consider that many original (non cracked) games with protections such as the ones from Rob Northen (ab)use this kind of exceptions to make the code very difficult to read.

So, even if you sometimes want to use the debugger to set some breakpoint, inspect memory, ..., firing the debugger on a non-configurable list of exceptions will do more harm than good IMO.


Mail converted by MHonArc 2.6.19+