why i like VS2008 debugger

[avansc]

disclaimer:
1. this is not even 5% of what you can do with the debugger, its mearly a few nice things. only two really, but one of them have saved me hours and hours of looking through thousands and thousands of lines of code.

2. by no means im i stating that this is the best debugger/IDE or anything of the nature.

3. i am also not saying that other debuggers/IDE cant do this.



this is kinda nifty. you can see all the dependencies and where you can find them. very nice if you are having trouble distributing a working copy.



this is really nice.
on the locals tab you see all the variables which is in the current function or piece of code you are in when a breakpoint or crash is reached.
notice the tree structure. you can go into any member var is see it value and memory location. this is great if you know X is suppose to be 10 but its 123456164, so then its alot easier to debug...

anyways, these are some of the things i use. but note that its only a small fraction of whats available to you.

note:
F11 - step into
F120- step over

[Kros]

/me high five.

[MarauderIIC]

I always prefer setting a watch to the locals, as the locals tends to show me stuff that I know I don't need to know. Autos is good sometimes though, because it'll tell you what a function returned.

[CC Ricers]

avansc, how did you get msvcrt.dll and msvcr90d.dll to load the symbols? I assume that these are the distributable dlls that need to go with your program. Also, there's an exclamation mark next to msvcr90d.dll when I'm debugging.