RE: [GD-Windows] RE:Strange debugging problem

[Josh M. <jm...@ri...>]

> This kind of problem is generally caused by having an=20
> expression in a watch list that invokes some code in your app=20
> that sometimes behaves oddly (e.g., hangs).

Now that you mention it, I've run into that a few times before. =20
Here are a few other things I'd consider:

- I've had mixed results with data breakpoints and conditional
breakpoints, so if you're using something besides F9 that might explain
the problem.

- VC6 had a bug that would occasionally cause my breakpoint list to
freak out, resulting in thousands of breakpoints and would also cause
weird hanging while debugging, but I haven't see that issue manifest in
7.1.  Hitting a breakpoint and/or stepping over a single statement would
take a really long time.  This is why I now always have the breakpoint
window visible :)

- Try inserting "__asm int 3;" at main/WinMain somewhere and see if that
sort of "manual" user breakpoint works.

- Start debugging with F11 (step in) instead of F5 (run) and see if it
works as expected.  Set a breakpoint on the next line and hit F5 (run)
and see if it hits.

- Reboot if you haven't in a while :)

- See if a new, default console app does the same thing.  If not...
=20
 - Delete the ncb file in your project directory (I think that's the
user config file?). =20

 - Clean solution, manually delete all output and intermediate files
that remain.  Quit, restart, rebuild all, run.