How to interpert exceptioninfo.txt

Problems compiling? Don't understand the source code? Don't know how to code your feature? Post here.

Moderator: Moderators

Locked
Naga
Posts: 45
Joined: 2003-12-02 11:24
Location: Sweden

How to interpert exceptioninfo.txt

Post by Naga » 2004-03-09 15:51

Hi,

how do I use the exceptioninfo.txt file to figure out what caused a crash? Is there a program or way to load the debug info and be able to see what happend?

--
Naga
newbe programmer

TheParanoidOne
Forum Moderator
Posts: 1420
Joined: 2003-04-22 14:37

Post by TheParanoidOne » 2004-03-09 17:35

It's a stack trace. It should show you the stack of methods being called during the crash.
The world is coming to an end. Please log off.

DC++ Guide | Words

Naga
Posts: 45
Joined: 2003-12-02 11:24
Location: Sweden

Post by Naga » 2004-03-10 04:18

so far I've got but is there any way of automaticly converting all those 0x????? chars to "real" data (human readable)?

Gasman1015
Posts: 184
Joined: 2003-05-26 11:29
Location: UK

Post by Gasman1015 » 2004-03-10 13:10

XP's Calculator.
Always remember you're unique, just like everyone else.

Naga
Posts: 45
Joined: 2003-12-02 11:24
Location: Sweden

Post by Naga » 2004-03-10 13:30

Doesn't that jst give an integer?
Since most items are <char>0x?????? this doesn't help much.

TheParanoidOne
Forum Moderator
Posts: 1420
Joined: 2003-04-22 14:37

Post by TheParanoidOne » 2004-03-10 13:48

Any hex numbers you finf will be memory addresses. What exactly are you trying to do?
The world is coming to an end. Please log off.

DC++ Guide | Words

Naga
Posts: 45
Joined: 2003-12-02 11:24
Location: Sweden

Post by Naga » 2004-03-11 03:21

if all those hex values are memory adresses they seem quite useless if there isn't a way of getting the actual data that was passed when the app crached.

I'm trying to learn how to debug an application and since i love DC++ I thought it would be a good thing to try and help while I'm learning.

arnetheduck
The Creator Himself
Posts: 296
Joined: 2003-01-02 17:15

Post by arnetheduck » 2004-03-11 04:41

The interesting part in that file is the stack of functions called...from that I can figure out the parameters passed most of the time, but just knowing how something crashed and on what line in the source code gives enough hints (for instance a c00000005 access violation on a pointer dereference means that the pointer was null or already deleted...etc...etc...), it takes some experience before you see this sort of things...
You're better off installing a debugger and jumping in to it when the app crashes, there's one free in the win32 platform sdk...use "attach to process" when the bug window pops up, and you'll be able to examine what's at the memory addresses, most variables etc...this becomes easier if you do a debug build as well...

Naga
Posts: 45
Joined: 2003-12-02 11:24
Location: Sweden

Post by Naga » 2004-03-11 04:49

Thanks for the tip. I'll be sure to use it next time (hopfully never :) )

Locked