Weird Debugging problem
-
In a program I've been working on for a while now I've started to have a weird debugging problem. When I hit a breakpoint and start stepping into other methods the debugger will take me to the middle of other methods instead (looking at the call stack the way I've reached the breakpoints is also incorrect, i.e. button click events been called randomly instead of when the user clicks the button). Has anyone came across this before? I've done the usual of doing a clean rebuild, shutting the machine down, swinging round on my chair whilst counting backwards from 100..... :mad: I'm working within Studio 2003. TIA
-
In a program I've been working on for a while now I've started to have a weird debugging problem. When I hit a breakpoint and start stepping into other methods the debugger will take me to the middle of other methods instead (looking at the call stack the way I've reached the breakpoints is also incorrect, i.e. button click events been called randomly instead of when the user clicks the button). Has anyone came across this before? I've done the usual of doing a clean rebuild, shutting the machine down, swinging round on my chair whilst counting backwards from 100..... :mad: I'm working within Studio 2003. TIA
i hope u have tried deleting the files in debug folder(should not leave any file).Then recompile the program.remove all th breakpoints and do start from first... :)
-
In a program I've been working on for a while now I've started to have a weird debugging problem. When I hit a breakpoint and start stepping into other methods the debugger will take me to the middle of other methods instead (looking at the call stack the way I've reached the breakpoints is also incorrect, i.e. button click events been called randomly instead of when the user clicks the button). Has anyone came across this before? I've done the usual of doing a clean rebuild, shutting the machine down, swinging round on my chair whilst counting backwards from 100..... :mad: I'm working within Studio 2003. TIA
It sounds like the .PDB file is out of sync.
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
-
In a program I've been working on for a while now I've started to have a weird debugging problem. When I hit a breakpoint and start stepping into other methods the debugger will take me to the middle of other methods instead (looking at the call stack the way I've reached the breakpoints is also incorrect, i.e. button click events been called randomly instead of when the user clicks the button). Has anyone came across this before? I've done the usual of doing a clean rebuild, shutting the machine down, swinging round on my chair whilst counting backwards from 100..... :mad: I'm working within Studio 2003. TIA
Actually, the problem is probably a corrupted .ncb file. Close the project, then delete the .ncb file and also delete any .aps or .clw file that may exist. Then reopen the project and you'll probably be OK. Hope that helps.
Karl - WK5M PP-ASEL-IA (N43CS) PGP Key: 0xDB02E193 PGP Key Fingerprint: 8F06 5A2E 2735 892B 821C 871A 0411 94EA DB02 E193
-
In a program I've been working on for a while now I've started to have a weird debugging problem. When I hit a breakpoint and start stepping into other methods the debugger will take me to the middle of other methods instead (looking at the call stack the way I've reached the breakpoints is also incorrect, i.e. button click events been called randomly instead of when the user clicks the button). Has anyone came across this before? I've done the usual of doing a clean rebuild, shutting the machine down, swinging round on my chair whilst counting backwards from 100..... :mad: I'm working within Studio 2003. TIA
Hi all, thanks for al of your replies. I tried all of them with no success and then finally found the answer on the MS Support site http://support.microsoft.com/?id=328784[^] This has fixed my problem and I think the problem crept into my program when I integrated some code that someone I work with wrote in a text editor (he switches between Linux and Windows) so this seems the likely culprit. Thanks all again, Andy