Can't Aynchronously break into win32 program ( Continued )

[Rosenbloom, Jack]

Sorry for the re-post. I lost posting access for a few weeks, have it
back, but wasn't able to reply to my original thread copied below

**** ORIGINAL THRED CONTENT****

I have a win32 program written in C++ compiled with OW1.9. I've been
evolving the code for years. In the past 6 months or so, I lost the
ability to to click the mouse on wdw.exe and break into the debugger.

Lost it: how? I.e. what actually happens if you try it now?

Are you aware of the limitations of this functionality as layed out in
the WD documentation, particularly the section "Interrupting a Running
Program --> Windows NT, Windows 95"?

****NEW REPLY****
I don't know how I lost the ability to break into this program using the
debugger. this is only true for one of my programs. All the others can
be asynchronously broken into. I'm assuming that there is something in
my program that prevents this from working. My question is what can
prevent the debugger from being able to break a running program. I want
to "adjust" my code to avoid this.

Thanks!
Jack

[r***@hotmail.com]

On Wed, 26 Nov 2014 18:26:41 +0100, Rosenbloom, Jack

Post by Rosenbloom, Jack
Sorry for the re-post. I lost posting access for a few weeks, have it
back, but wasn't able to reply to my original thread copied below
**** ORIGINAL THRED CONTENT****

I have a win32 program written in C++ compiled with OW1.9. I've been
evolving the code for years. In the past 6 months or so, I lost the
ability to to click the mouse on wdw.exe and break into the debugger.

Lost it: how? I.e. what actually happens if you try it now?
Are you aware of the limitations of this functionality as layed out in
the WD documentation, particularly the section "Interrupting a Running
Program --> Windows NT, Windows 95"?
****NEW REPLY****
I don't know how I lost the ability to break into this program using the
debugger. this is only true for one of my programs. All the others can
be asynchronously broken into. I'm assuming that there is something in
my program that prevents this from working. My question is what can
prevent the debugger from being able to break a running program. I want
to "adjust" my code to avoid this.

I have never used the break into functionality, I think I tried once and
found it unreliable. I would make a keyboard/accelerator/menu handler
in the message loop, that emits a int(3) on activation. That puts you in
the debugger every time, in a reliable manner.

Roald

[Rosenbloom, Jack]

Thanks for the reply Roald. This feature has always been reliable until
recently. However, your suggestion is a good one which will work fine
for me.

Thanks again!

Jack