Breakpoints are ignored (the red circles disappear as the program starts) around half the time I run my program, the other half of the time it works fine. Basically I have to quit my program and restart it if I notice the breakpoints disappear. Is there a better solution?
Asked
Active
Viewed 64 times
0
-
What language is this? Are you running optimized code or code in Release mode? – Dai Feb 16 '15 at 23:53
-
I am amazed VS2003 works at all on Windows 7. Tried it elevated? – Rob Feb 17 '15 at 00:01
-
Yes, the better solution is to get Visual Studio 2013 Express and spend the time to convert your project(s). – Chris O Feb 17 '15 at 00:01
-
You got a warning, "This program has known compatibility issues", when you installed it. Now you know what they look like. Well, some of them. – Hans Passant Feb 17 '15 at 00:08
-
possible duplicate of [Has anyone managed to get Visual Studio 2003 running on Windows 7?](http://stackoverflow.com/questions/879082/has-anyone-managed-to-get-visual-studio-2003-running-on-windows-7) – Hans Passant Feb 17 '15 at 00:08
-
Dai - language is C, I'm not sure the definition of "optimized code" but I am running in Debug mode (as opposed to Release mode) As for why I'm using VS 2003 on Windows 7, that's just how things are Hans - I've unsuccessfully tried suggestions on that page including: - running as Admin - setting application compatibility to Windows Vista SP2 and WinXP SP3 - closing pdb file handles (it opens a new one each time not closing the old, but this seems unrelated to whether or not I can debug) – Adventurous Feb 17 '15 at 19:08
2 Answers
0
You stated VS2003, are you sure you meant 2003 and not 2013? Can you clarify the language (C#, VB?); Also are you building a console app, windows, app, web, etc?
In all cases the breakpoints do work in VS Studio. They can be unreachable if you are making edits to your program without restarting. Or if you are changing code that is not re-compiled into the dll you are stepping into.
user3303569
- 153
- 1
- 1
- 6
-
C, win32 project, not editting, just running and closing the program and it only hits breakpoints sometimes – Adventurous Feb 17 '15 at 19:10
0
This seems to fix it:
-detach the process
-reattach it
Now it hits the breakpoints
Adventurous
- 81
- 7