PDA

View Full Version : Debugger Halo Exception?


Matooba
October 18th, 2009, 02:03 PM
Is there a debugger or a way to set one up for ingame Gathering Exception Data?
CodeBrain
October 18th, 2009, 02:07 PM
No.

I don't believe it's possible (without Open Sauce anyway)

Me and ShadowSpartan believe that the Gathering Exception Data thing is mainly a leftover product from Halo CE, since probably before Halo did problem reports, it just showed the Gathering Exception Data error, instead of the report. When they made it do problem reports, they just left the code in there because they thought no one would trigger it.

At least, that's what I believe.
CrAsHOvErRide
October 18th, 2009, 02:25 PM
It does what it suppose do...show where the exception occurred. Attach a debugger and recreate the problem and you'll see where it breaks.
Matooba
October 18th, 2009, 02:32 PM
Whats a good debugger to use?
Cheat Engine (5.2) or Kernal Debugger?

I've been able to search the RAM, but not attach debugger in order to set breakpoints.
ShadowSpartan
October 18th, 2009, 03:47 PM
It does what it suppose do...show where the exception occurred. Attach a debugger and recreate the problem and you'll see where it breaks.
He's talking about Halo's own exception system, not the problem report that Windows automatically generates when a program crashes. He had hoped the Halo exception data would have meaningful information to the average modder, such as "game exceptioned while loading warthog.model_animations tag". Just having the address in the executable where it crashed isn't going to help a modder if they have no prior reverse engineering experience.
CrAsHOvErRide
October 18th, 2009, 04:04 PM
Yeah I was talking from a RE point of view. Matooba, it requires a lot of experience and the problem will not as obvious as you might think (it could be a divide by 0 error but you don't know in what context etc).
Matooba
October 19th, 2009, 09:47 PM
I see your point, thanks for the help none the less.
Skarma
October 20th, 2009, 03:49 AM
Use OllyDbg (http://ollydbg.de/), its the best around I think. If you have never used a debugger before, it won't make any sense unless you know how x86 assembler works. What you trying to figure out?


It does what it suppose do...show where the exception occurred. Attach a debugger and recreate the problem and you'll see where it breaks.Great advice, do what this man says