Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!stanford.edu!morrow.stanford.edu!news
From: GD.SAR@forsythe.stanford.edu (Sandy Rockowitz)
Newsgroups: comp.os.os2.programmer
Subject: Re: Looking for OS/2 debugging tools
Message-ID: <1991Mar23.213716.10427@morrow.stanford.edu>
Date: 23 Mar 91 21:37:16 GMT
Sender: news@morrow.stanford.edu (News Service)
Distribution: usa
Organization: Data Center, Stanford University, California, USA
Lines: 34

In article <9425@cognos.UUCP>,
roberts@cognos.UUCP (Robert Stanley) writes:
>I am looking for information about debugging tools for multi-tasking
>OS/2 applications.
>
>I am also interested in first-hand experience with any such product,
>particularly with regard to usefulness and/or serious deficiencies.
>
I've been using the Multiscope debugger recently to debug a
multi-threaded communication prgram written in Modula-2.  While
the user interface is very attractive, I haven't found it very
robust.  I've hung it any numbers of times, and usually a
reboot is required.  For debugging the asynchronous program, I
found it more useful to create a named pipe to an output program
in a windowed session and send debugging trace messages to that
program.

Another aspect that I found frustrating, in my situation, was that
I was debugging a line mode application on a two monitor system,
but Multiscope doesn't allow you to run the program being debugged
on the second monitor and the debugger on the VGA monitor under PM.
If you want to use two monitors, you must use the non-PM
debugger.

A new release of the debugger should be out within the next few
months (the last date I heard was April, but since I don't
believe the product has yet been released for beta testing, I
doubt it).  So hopefully many of these problems will be resolved.
But for now, I'm looking forward to getting back to coding in
C so that I can use Codeview.  While it isn't nearly as slick,
it's definitely more robust.

Sanford Rockowitz
GD.SAR@FORSYTHE.STANFORD.EDU