Debugger skipping new code ?????

[SteveB]

Hi

Out of nowhere a project I am working on has suddenly started ignoring
new code when debugging. What happens is that any new code will accept
a break point when building but after I hit the break point the
debugger jumps to the next line of code I haven't added and debugs
from there !!! The break point is also moved, when I stop debugging
the break point jumps back to where it was. This is happening on 3
speperate machine and I suspect may be related to a recent restore
from Source Safe that was performed a few weeks ago - this is the
first time in a month we have amended this particular project.

Any ideas ?

Thanks

Steve

[m***@gmail.com]

Did you try to set breakpoint after rebuilding the code? It may solve
your problem. If not check followings:

1. Check if you have set a breakpoint in an explicitly loaded DLL
(loaded with LoadLibrary API call). All COM DLL are explicitly loaded
DLL. So manually add these DLLs to the "Additional DLLs" list
(Projects -> Settings... ->Debug Tab->"Additional DLLs" in the
Category combo box) to load symbols for those DLLs when you start
debugging.

2. Check if you set compiler optimization. Sometime for compiler
optimization debugger can't resolve the breakpoint location.

Thanks,
- Mahatab

Post by SteveB
Hi
Out of nowhere a project I am working on has suddenly started ignoring
new code when debugging. What happens is that any new code will accept
a break point when building but after I hit the break point the
debugger jumps to the next line of code I haven't added and debugs
from there !!! The break point is also moved, when I stop debugging
the break point jumps back to where it was. This is happening on 3
speperate machine and I suspect may be related to a recent restore
from Source Safe that was performed a few weeks ago - this is the
first time in a month we have amended this particular project.
Any ideas ?
Thanks
Steve

[SteveB]

Post by m***@gmail.com
Did you try to set breakpoint after rebuilding the code? It may solve
1. Check if you have set a breakpoint in an explicitly loaded DLL
(loaded with LoadLibrary API call). All COM DLL are explicitly loaded
DLL. So manually add these DLLs to the "Additional DLLs" list
(Projects -> Settings... ->Debug Tab->"Additional DLLs" in the
Category combo box) to load symbols for those DLLs when you start
debugging.
2. Check if you set compiler optimization. Sometime for compiler
optimization debugger can't resolve the breakpoint location.
Thanks,
- Mahatab

Post by SteveB
Hi
Out of nowhere a project I am working on has suddenly started ignoring
new code when debugging. What happens is that any new code will accept
a break point when building but after I hit the break point the
debugger jumps to the next line of code I haven't added and debugs
from there !!! The break point is also moved, when I stop debugging
the break point jumps back to where it was. This is happening on 3
speperate machine and I suspect may be related to a recent restore
from Source Safe that was performed a few weeks ago - this is the
first time in a month we have amended this particular project.
Any ideas ?
Thanks
Steve- Hide quoted text -

- Show quoted text -

2 was spot on - although i fouond it independently of this post ...
optimisation had been set to full with all options checked and hence
my test code was optimised out - one to check for in the future i
think ...