Unable to reach breakpoint in Visual Studio

Question

I am facing a odd behavior of Breakpoints in Visual Studio 2010 Express. Below is the code with breakpoints.

enter image description here

I am able to break at the first breakpoint (Line 159), but stepping after line 160, the cursor vanishes, i.e after this image of code pressing F10/F11 the application is displayed.

The problem is,

Why isn't line 162 executing (Without this statement, asserts fail elsewhere) or breaking at it?

Note : The line 166 Refresh(); is being executed, because the application displayed is updated.

EDIT : On suggestions in comments, I stepped through disassembly, and I found this line (from wxWidgets library) is causing the debug to fail 00D5AF7C call wxCharBuffer::~wxCharBuffer (0D207AAh)

If the code is compiled in Release mode, the line in question could be optimized out. Try compiling the code in Debug mode. — Phillip Ngan, Jan 26 '12 at 06:18
Check that the /Od compiler is present. This disables code optimization. — Phillip Ngan, Jan 26 '12 at 06:23
Have you changed the code since last build, or since you started debugging? Have you tried a rebuild-all? — Some programmer dude, Jan 26 '12 at 06:25
Do full rebuild first. That helps 99% of time. Then, start commenting out memory modifying lines — Ulterior, Jan 26 '12 at 06:29
@JoachimPileborg: Since last build I only added line 162. And on your suggestion, tried Rebuild solution. But no help :( — Vinayak Garg, Jan 26 '12 at 06:33
Have you tried stepping through disassembly? With combined assembly-source view you can tell what exactly is going on. — gwiazdorrr, Jan 26 '12 at 08:19
@gwiazdorrr: How do I start stepping through assembly code? As in from first breakpoint. — Vinayak Garg, Jan 26 '12 at 08:26
Once you hit a breakpoint go to Debug->Windows->Disassembly. Or just click RMB and then "Go to disassembly". — gwiazdorrr, Jan 26 '12 at 08:29
@gwiazdorrr: Thanks, that was convenient! I have rounded on to a assembly line, after which the havoc wreaked :D. — Vinayak Garg, Jan 26 '12 at 08:37
@gwiazdorrr: Disassembly helped solve my problem, i got rid of `wxCharBuffer`. You should consider adding your comment as answer. :) — Vinayak Garg, Jan 26 '12 at 11:06
@VinayakGarg you got your answer already but just as an FYI, I sometimes find deleting bin, obj directories then full rebuild resolves this error — Dr. Andrew Burnett-Thompson, Jan 26 '12 at 12:07
@Dr.AndrewBurnett-Thompson: Thanks, I will remember. BTW i have used this method when installing packages in Linux. — Vinayak Garg, Jan 26 '12 at 12:21

score 2 · Accepted Answer · answered Jan 26 '12 at 12:03

2

Have you tried stepping through disassembly? With combined assembly-source view you can tell what exactly is going on.

To do that once you hit a breakpoint go to Debug->Windows->Disassembly. Or just click RMB and then "Go to disassembly".

answered Jan 26 '12 at 12:03

gwiazdorrr

6,181
2
27
36

Unable to reach breakpoint in Visual Studio

1 Answers1