PF> This is actually the best way to debug many PM 
 PF> programs (by running the
 PF> debugger in a full-screen text session).

 CH> If you have two monitors.  Otherwise, you'll never be 
 CH> able to see what you're doing.

I have two monitors,  but I never use it for this purpose.  I use the
watcom full screen debugger in the same monitor as pm.

 CH> I can't believe that I can't switch away from a full 
 CH> screen debugg session while single steping a window 
 CH> procedure because the system will hang.

Why would you want to?  I know of this 'problem' (it is actually a
limitation of OS/2's DosDebug&PM design),  so simply avoid it.

IBM's debugger has a trick to make this work some of the time (they call it
"asynchronous debug mode",  where queue messages for the halted
debugee are intercepted -- clever but rarely reliable).

   > No wonder PM
 CH> programs tend to have more bugs in them than VIO ones -
 CH>  the debuggers aren't worth a %^&*.

The only time PM debugging becomes complicated, IMO,  is when you want to
run two PM programs under a debugger at the same time on the same pc;this
is not hard either,  but you have to be careful to avoid a deadlock.

 CH> It looks like I'll just have to get FP17 to fix the 
 CH> SIQ problem and get into the habit of not running much 
 CH> else while debugging.

You can run as many programs as you like -- you just can't move the input
focus to them (and fp17 will not fix this) in synchronous mode.


--- Maximus/2 3.00