Stepping through code opens disassembly window

[Joep]

Hi, recently I have some issues debugging in VS6. Stepping into some
functions is only possible when I set a breakpoint in that function.
Otherwise the disassembly Window is opened and the debugger seems to stop
doing his work (app keeps running after pressing F5, but no breakpoints are
picked up anymore).

Is there anyone out there who could shed some light on this?

regards,
Joep

(yes I know the discussions about upgrading, but this is an app which
heavily relies on DAO, which is not upgradable to knewer Visual Studio
versions and porting it to something else would mean a complete rewrite)

[Michael Viking]

Not sure it will help, but what I'd do in this situation is remove all
breakpoints and close Visual Studio. Then I'd completely clean everything
completely (by deleting debug directories) including automatically generated
files like ncb files and then make sure the autoexp.dat (which has
NoStepInto info) file looked right. Then I'd restart VS, make sure all the
settings for building debug versions are correct (no optimizations, generate
debug info, for example), then rebuild and see what happens.
Probably won't help, but good luck!
-Michael Viking

Post by Joep
Hi, recently I have some issues debugging in VS6. Stepping into some
functions is only possible when I set a breakpoint in that function.
Otherwise the disassembly Window is opened and the debugger seems to stop
doing his work (app keeps running after pressing F5, but no breakpoints are
picked up anymore).
Is there anyone out there who could shed some light on this?
regards,
Joep
(yes I know the discussions about upgrading, but this is an app which
heavily relies on DAO, which is not upgradable to knewer Visual Studio
versions and porting it to something else would mean a complete rewrite)