🔒 Locked

A problematic debugging question

Started by Dark Rain Aug 9, 2002 at 12:48 PM 2 replies 250+ views

Original Post

Aug 9, 2002 at 12:48 PM

This morning when I compiled my engine, I had a crash on exection. I had forgoten what exactly it is that I changed, no big deal I thought, I'll just run the debugger. My problem is that nothing happen in debug mode and nothing in release build. It's just a problem that happen when I run it in a debug build without being in debug mode. I get the classic "Application Error" and the memory adress of the problem with "The memory could not be "read" ". I tried tracking it down by commenting out bits and piece of my code but I wound up in a part I havent update in a while and I honestly cant see what the error is. Any debugging veterans here could offer a suggestion? [edited by - Dark Rain on August 9, 2002 1:48:49 PM]

Tornado

Aug 9, 2002 at 1:42 PM

Hmmm very problemetic

I think you can find the offending function, try this:
- Goto your project settings, under the Link tab select - Create MAP file.
- Recompile your project. Now goto the debug directory and load: (project_name).map in Notepad or something.

Now, when you get the error message (About the access violation), write it down (Don't write the address that the command was trying to access, write down the address of the command

).
Now goto your map file and try to find in which function that command was...
Let's say the naughty instruction is at 0x00000330 (For example). And in your .map file you have the following:
0001:00000320 ?HTTP_Init@@YAXXZ
0001:00000390 ?HTTP_UnInit@@YAXXZ

Then the offending instruction is in function HTTP_Init(). See where I'm going here?

I never tried debugging this way, but it should work.
Goodluck finding the problem

Goblineye Entertainment
The road to success is always under construction

[edited by - Tornado on August 9, 2002 2:50:11 PM]

Dark Rain

Aug 9, 2002 at 2:15 PM

Thanks a lot for the help, I'll remember that trick in the future. I finaly found the offending bug tho, a file had gotten corrupted somehow and for some reasons, it crashed only under these conditions. *shrug* weird, I'm not too sure I see why but ah well.

[edited by - Dark Rain on August 9, 2002 3:15:47 PM]

Tornado

Aug 9, 2002 at 5:12 PM

quote:
Original post by Dark Rain
Thanks a lot for the help, I''ll remember that trick in the future.

Yup, very nice... Just hope I never have to use it

If you want to know more, like the exact instruction that causes the fault, check this out: http://www.candle.com/www1/cnd/portal/CNDportal_Article_Master/0,2245,2683_2947_46042,00.html.

Goblineye Entertainment
The road to success is always under construction

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.