🔒 Locked

msvc++ debugger questions

Started by Cat_B Jan 1, 2003 at 10:47 PM 5 replies 200+ views

Original Post

Jan 1, 2003 at 10:47 PM

Hi, Do you know where I can find an online tutorial on how to use it? I googled but got alot of nothing. Also, do you guys really use the debugger?? I''m not a professional programmer and I have always just used print statements. But the thing with opengl on win32 is there is nowhere to print, lol, or at least I don''t know how to open up a "printing window" on top of the graphics window.. Anyhow, if you "real" programmers really do think the debugger is great then its time I learn. But I''ve diddled with it and it''s over my head. Thanx alot Cat

Colin Jeanne

Jan 2, 2003 at 1:15 AM

I use the debugger all the time. It is probably more useful than many features of the IDE itself.

I think that this should be all you ever needed to know about the debugger.

As for printing your errors. I suggest printing them to a file (with proper information so that you can track them down). I found that especially helpful when I was working with fullscreen DirectDraw.

The hackers must have gotten into the system through the hyperlink!!
Invader''s Realm

mutex

Jan 2, 2003 at 3:24 AM

I always run things in debug mode. It''s convenient when your program crashes, because you know where it crashed instead of having to start it in the debugger later and trying to reproduce the problem.

Cat_B

Jan 2, 2003 at 12:02 PM

OK, Thanx for the tips then I will learn this debugger...

I have looked at the MSDN info on the debugger, thank you. I must be learning disabled or somthing- I like the MSDN for reference but for actually learning new concepts I can never really follow it. Does anyone know of a gentle-type tutorial on the net to just get me going with the debugger? I can''t find one so I probably AM learning disabled!. Somthing to explain all the "stack" gibberish or whatever it is that I see.

Thanx

Stoffel

Jan 2, 2003 at 1:03 PM

IMHO, debugging should be a requisite college course. It''s _the_ most important tool in a programmer''s toolchest. Its value cannot be overstated.

The "stack" you see is the call stack. In C, you have your main function, which calls other functions, which calls other functions. If you set a breakpoint in an arbitrary function, your call stack will show the current function at the top of the stack and main at the bottom.

Note: I don''t think any compilers actually call main "main" anymore, so you might see something that looks like main, but not quite.

T h i n k L i b e r a l l y .

Topic Locked

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