🚀 go-pugleaf

In article <lwjnw_.daveb@netcom.com> daveb@netcom.com (Dave Briccetti) writes:
>Alfred.Kayser@dnpap.et.tudelft.nl (Alfred Kayser) writes:
>: Help, I have a problem with a PM program. When I open a (WinCreateStdWindow)
>: standard window, but which is hidden, and I show it using
>: a WinShowWindow, PM sends me a WM_ACTIVATE message. So far so good,
>: I set the 'active' flag and returns FALSE. So far as is documented, but
>: PM crashes and gives a protection violation. Help I'm lost in PM!!!
>: 
>Perhaps you could run the program under a debugger and find out exactly
>where you are crashing.

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. 

Better, you should insert fprintf() statements everywhere and log the
program's position to a file and find out what gets written just
before the crash.  Later, you can #ifdef them out, so you can always
set a define to re-compile your code in debug mode.  (I usually use an
#ifdef DEBUG for this)


-- 
   |)  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