Debug stepping problem in VS2008

[Les_Neilson]

I am stepping through some code to find a particularly elusive bug, which means I have a lot of windows open in VS. Quite often (eg 3 times this morning) I press F11 to step into a routine, then press F10 to beginstepping through the code - mostly the first few statements are simple initialisations eg x=0.0- but when I press F10 again the debugger jumps to the next breakpoint (if there is one)! So I often have to restart the exe to get back to where I was.

Anyone experienced this?
Or it could be a fault in my keyboard :-(

Les

[jirina]

It might not be the same behavior, but when I press F11 to step into a subroutine or a functions whose call takes more than 1 row in the source code (I use + sign in the 6th column to continue a command), I need to repeeat that several times before I really step into the subroutine.

I am using VS 2008 and IVF 11.0.061.

[Les_Neilson]

Quoting - jirina

It might not be the same behavior, but when I press F11 to step into a subroutine or a functions whose call takes more than 1 row in the source code (I use + sign in the 6th column to continue a command), I need to repeeat that several times before I really step into the subroutine.

I am using VS 2008 and IVF 11.0.061.

Yes that happens with F11 and with F10,for continued statements, especially if any actual arguments are subscripted. Sometimes F11 takes several seconds before the source code appears, and occasionally VS will die after several seconds (this is on Vista but alsohappened on XP) :-(
No one at work seems to have experienced my current problem - f10 stepping suddenly jumping to next breakpoint - so I am thinking I have a suspect keyboard.

Les

[Jeffrey_A_Intel]

Quoting - Les Neilson

No one at work seems to have experienced my current problem - f10 stepping suddenly jumping to next breakpoint - so I am thinking I have a suspect keyboard.

A quick check would be todebug ona co-worker's system.Or to use someone else's keyboard on your system.

[Les_Neilson]

Quoting - Jeff Arnold (Intel)

A quick check would be todebug ona co-worker's system.Or to use someone else's keyboard on your system.

True on both counts. The trouble is the F10 problem is intermittent (and F11 too)- happened at least 3 times yesterday morning, not once today :-)
Our systems people recently replaced all our hardware, I wanted to keep my old keyboard but they wouldn't let me.

Les

[jimdempseyatthecove]

Les,

As I do not have VS2008 I cannot attest to the quirkyness of WinDbg of that version.

However, as a band-aid to get you by, can you define a debugger keyboard macro and hot key to perform

DownArrow, Ctrl-F10


Jim Dempsey

[Steve_Nuchia]

This may not be relevant but if you're debugging optimized code this sort of thing happens because the debugger implements source-level stepping by setting breakpoints where it thinks it needs them but it occasionally gets confused with optimized code. At least I think that's what happens.

But it should be repeatable if that's the issue.

[g_f_thomas]

Quoting - Les Neilson

True on both counts. The trouble is the F10 problem is intermittent (and F11 too)- happened at least 3 times yesterday morning, not once today :-)
Our systems people recently replaced all our hardware, I wanted to keep my old keyboard but they wouldn't let me.

Les

This may be silly, but does tha same happen when you use the mouse to pick from the Debug menu instead of the keyboard?

Gerry

[Les_Neilson]

Jim : keyboard macro - thanks I'll take a look.
Steve : I have come across the problem of optimised debug code, but in this instance optimisation is off.
Gerry : I haven't tried just using the mouse and menus but might give it a try.

My inclination is to suspect my system. Twice in two days I have had a Blue Screen. :-((

Les