Is it your program that is being debugged that is generating the exception, or is it the Visual
Studio debugger itself causing the exception?
There have been a few bugs (not many, though) with this type of thing. It would help to know the
specific code involved where the breakpoint is set. Is this an optimized build, or is optimization
off for debugging? Do you already have SP1 applied?
SP1 is installed. It is a debug (no optimization) build. There
doesn't appear to be anything special about the line of code, since it
happens on *any* breakpoint I set. I could set it on line 20, 200,
2000, or anything in-between.
I'm beginning to suspect it has something to do with one of the dlls
that gets delay-loaded, but I can't be certain. The reason I think
this is because I can set a breakpoint very early (in main()), but
after stepping over a few lines it will eventually exhibit the
crashing symptoms and only right after a flurry of
'myapp.exe': Loaded 'c:\...\whatever.dll', Symbols loaded.