Path: utzoo!utgpu!news-server.csri.toronto.edu!csri.toronto.edu!drz
Newsgroups: comp.os.os2.programmer
From: drz@csri.toronto.edu (Jerry Zarycky)
Subject: Debugging under Presentation Manager
Message-ID: <1990Aug31.160814.22637@jarvis.csri.toronto.edu>
Organization: CSRI, University of Toronto
Date: 31 Aug 90 20:08:14 GMT
Lines: 31

I've been programming under Presentation Manager for the last 6 months
or so, and I have a question about source-level debugging a Presentation
Manager application under either CodeView or LogiTech's Multiscope.

Debugging seems to work fine until I try to debug a Window Procedure.

Whenever I hit the first breakpoint which happens to be within a window
procedure, I can display all the things that I wish within the debugger.
However, if I try to resume the program after examination of the variables,
I find that the program "locks up", (i.e.) it doesn't respond to messages
any more, even though I can still move the mouse pointer around.
After a while, Presentation Manager will tell me that this program
isn't responding any more, and asks me if I want to terminate it.
Even though I say "OK", the system is still hung and I have to reboot.

Does this sound familiar to anyone else?
Is there anything that I can do to get around this problem AND still use
the debuggers that I have paid for?
Any answers would be appreciated, since I'm getting tired of "printf"
statements!

Oh, and I want to emphasize that debugging non-Presentation Manager
applications works fine, but then again, I don't need a fancy debugger
(usually) to debug those.


Jerry Zarycky

Usenet:	{uunet,watmath}!csri.toronto.edu!drz
CSNET:	drz@csri.toronto.edu         EAN:   drz@csri.toronto.cdn
BITNET:	drz@csri.utoronto