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 author=Adron link=board=30;threadid=4988;start=0#msg41727 date=1075418365]
Step over C library functions instead of tracing into them?
[/quote]

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 author=Adron link=board=30;threadid=4988;start=0#msg41750 date=1075421441]
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]

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 author=Maddox link=board=30;threadid=4988;start=0#msg41752 date=1075422100]

Right, but for some reason I thought trace into would only go into functions directly associated with the project. ::)
[/quote]

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 author=Adron link=board=30;threadid=4988;start=0#msg41876 date=1075504588]
[quote author=Maddox link=board=30;threadid=4988;start=0#msg41752 date=1075422100]

Right, but for some reason I thought trace into would only go into functions directly associated with the project. ::)
[/quote]

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]

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

[quote author=Maddox link=board=30;threadid=4988;start=0#msg41911 date=1075514853]
[quote author=Adron link=board=30;threadid=4988;start=0#msg41876 date=1075504588]
[quote author=Maddox link=board=30;threadid=4988;start=0#msg41752 date=1075422100]

Right, but for some reason I thought trace into would only go into functions directly associated with the project. ::)
[/quote]

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]

The thing is, it doesn't step into API functions, just functions in the standard C library.
[/quote]
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 author=Skywing link=board=30;threadid=4988;start=0#msg41916 date=1075515858]
[quote author=Maddox link=board=30;threadid=4988;start=0#msg41911 date=1075514853]
[quote author=Adron link=board=30;threadid=4988;start=0#msg41876 date=1075504588]
[quote author=Maddox link=board=30;threadid=4988;start=0#msg41752 date=1075422100]

Right, but for some reason I thought trace into would only go into functions directly associated with the project. ::)
[/quote]

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]

The thing is, it doesn't step into API functions, just functions in the standard C library.
[/quote]
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]

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

[quote author=Maddox link=board=30;threadid=4988;start=0#msg41918 date=1075517278]
It does it for any C library I try to link.
[/quote]
You should probably either install the CRT source like Adron recommended, then, or use a different debugger. Personally, I'd go with WinDbg.

[quote author=Skywing link=board=30;threadid=4988;start=0#msg41925 date=1075520006]
[quote author=Maddox link=board=30;threadid=4988;start=0#msg41918 date=1075517278]
It does it for any C library I try to link.
[/quote]
You should probably either install the CRT source like Adron recommended, then, or use a different debugger. Personally, I'd go with WinDbg.
[/quote]

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.