Valhalla Legends Archive

This dialog box keeps popping up everytime an ANSI C function appears when stepping through code while debugging. If I hit cancel then it switches to the disassembly view. Anyone know of a fix?

Step over C library functions instead of tracing into them?

Quote from: Adron on January 29, 2004, 05:19 PM
Step over C library functions instead of tracing into them?

argh...

Well, I typically walk through my programs with step over. Only when I want to examine the internals of some function do I trace into...

Quote from: Adron on January 29, 2004, 06:10 PM
Well, I typically walk through my programs with step over. Only when I want to examine the internals of some function do I trace into...

Right, but for some reason I thought trace into would only go into functions directly associated with the project.  

Try a different debugger, that would definately solve it.  Either windbg or softice or something like that might work better.

Quote from: Maddox on January 29, 2004, 06:21 PM

Right, but for some reason I thought trace into would only go into functions directly associated with the project.  

I'm not sure how to set the debugger to only step into some functions. Windbg & co are all likely to step into api functions as well. Maybe you should just get used to hitting step over?


Oh, and go install those sources to your hard drive, so you won't be prompted about them all the time.

Quote from: Adron on January 30, 2004, 05:16 PM

Quote from: Maddox on January 29, 2004, 06:21 PM

Right, but for some reason I thought trace into would only go into functions directly associated with the project.  

I'm not sure how to set the debugger to only step into some functions. Windbg & co are all likely to step into api functions as well. Maybe you should just get used to hitting step over?


Oh, and go install those sources to your hard drive, so you won't be prompted about them all the time.

The thing is, it doesn't step into API functions, just functions in the standard C library.

Quote from: Maddox on January 30, 2004, 08:07 PM

Quote from: Adron on January 30, 2004, 05:16 PM

Quote from: Maddox on January 29, 2004, 06:21 PM

Right, but for some reason I thought trace into would only go into functions directly associated with the project.  

I'm not sure how to set the debugger to only step into some functions. Windbg & co are all likely to step into api functions as well. Maybe you should just get used to hitting step over?


Oh, and go install those sources to your hard drive, so you won't be prompted about them all the time.

The thing is, it doesn't step into API functions, just functions in the standard C library.

Perhaps you are using the static link CRT and thus the functions are included in your program image?  It could also be that it thinks it has debug info with lines for those functions.

Quote from: Skywing on January 30, 2004, 08:24 PM

Quote from: Maddox on January 30, 2004, 08:07 PM

Quote from: Adron on January 30, 2004, 05:16 PM

Quote from: Maddox on January 29, 2004, 06:21 PM

Right, but for some reason I thought trace into would only go into functions directly associated with the project.  

I'm not sure how to set the debugger to only step into some functions. Windbg & co are all likely to step into api functions as well. Maybe you should just get used to hitting step over?


Oh, and go install those sources to your hard drive, so you won't be prompted about them all the time.

The thing is, it doesn't step into API functions, just functions in the standard C library.

Perhaps you are using the static link CRT and thus the functions are included in your program image?  It could also be that it thinks it has debug info with lines for those functions.

It does it for any C library I try to link.

Quote from: Maddox on January 30, 2004, 08:47 PM
It does it for any C library I try to link.

You should probably either install the CRT source like Adron recommended, then, or use a different debugger.  Personally, I'd go with WinDbg.

Quote from: Skywing on January 30, 2004, 09:33 PM

Quote from: Maddox on January 30, 2004, 08:47 PM
It does it for any C library I try to link.

You should probably either install the CRT source like Adron recommended, then, or use a different debugger.  Personally, I'd go with WinDbg.

Ah ok, thanks.

Edit: nevermind

I'm pretty sure the bottom issue is that he has debug info with lines for them. Removing that would solve the problem, but having lines and source code for the C libraries is a good thing when you run into some assertion deep in them.