🚀 go-pugleaf

In article <1992Sep03.150929.24455@ans.net> db3l@ans.net (David Bolen) writes:
>In article <d#lnmz+.daveb@netcom.com> daveb@netcom.com (Dave Briccetti) writes:
>>dic5340@hertz.njit.edu (David Charlap) writes:
>>: Not really.  You'll have to remote-debug it.  You can't run a debugger
>>: on the same machine as the PM code you're debugging.  It halts lots of
>>: things. 
>>
>>What???  I've been doing it for years.  Occasionally I'll have to put
>>printf's in, but most of the time I do quite well with Codeview or IPMD.
>
>Well, I think David's comment should have been more along the lines of it can
>be somewhat difficult (or dangerous perhaps?) to run a debugger on the same
>machine as the PM code you are developing, but it's not impossible.  And until
>IPMD that debugger had to be a text mode debugger (ie: you couldn't use
>Multiscope in PM mode when debugging PM applications), and you had better make
>sure not to stop your program at a breakpoint in a message procedure and then
>Ctrl-ESC out of the debugger back to the PM screen.  Instant system hang.

OK. I normally debug code by single-stepping it through functions.
This clobbers a PM program if you do it on the same machine, since
single-stepping is the same as placing a breakpoint at every line.
-- 
   |)  David Charlap           "TELEPHONE, n.  An Invention of the devil which
  /|_  dic5340@hertz.njit.edu   abrogates some of the advantages of making a
 ((|,)                          disagreeable person keep his distance."
  ~|~                              --- Ambrose Bierce, The Devil's Dictionary