Path: utzoo!attcan!uunet!samsung!usc!rutgers!cmcl2!sbcs!csserv1!cfreas
From: cfreas@csserv1.ic.sunysb.edu (Terry Freas)
Newsgroups: comp.os.os2.programmer
Subject: Re: OS/2 profiler
Message-ID: <1990Oct26.192403.28268@sbcs.sunysb.edu>
Date: 26 Oct 90 19:24:03 GMT
References: <1990Oct24.152750.2775@sbcs.sunysb.edu> <11126@hubcap.clemson.edu>
Sender: usenet@sbcs.sunysb.edu (Usenet poster)
Organization: State University of New York at Stony Brook
Lines: 20

In article <11126@hubcap.clemson.edu> lsalomo@hubcap.clemson.edu (lsalomo) writes:
>From article <1990Oct24.152750.2775@sbcs.sunysb.edu>, by cfreas@csserv1.ic.sunysb.edu (Terry Freas):
>> to gain ownership of it, so what's to be done?  The new Multiscope (1.1?)
>> under PM can debug PM programs, but does it actually debug the PM
>> thread in the program's window procs?  If so, how?
>
>The new Multiscope can debug PM programs?  Is the PM program debugger (see
>below) a PM application in itself?
>
>The last time I used Multiscope, it had a PM debugger written in text mode,
>and a debugger for text programs written in PM.

Yes.  I just received Multiscope's newest specs (v1.1) that allow a PM
program to be debugged by the PM program.  It seems OS/2 v1.1 was at
fault, not Multiscope.  Wouldn't be worth it without a high-res screen,
though.

-- 
oo            - I live for the day earth becomes a domain name -            oo
\/ Jeremy Wohl / wohl@max.physics.sunysb.edu / cfreas@csserv1.ic.sunysb.edu \/