roberts@cognos.UUCP (Robert Stanley) (03/22/91)
I am looking for information about debugging tools for multi-tasking
OS/2 applications. By this I mean a logical application comprising
several, asynchronous, concurrently executing processes, each of which
is a multi-threaded executable. Inter-process communication may be
local or networked. I do, of course, have the CodeView that comes
with the Microsoft development environment.
Thus far I have heard two tools mentioned:
RTD - a Real-Time Debugger
MultiScope from Logitech
I have a small amount of information about MultiScope, and none for
RTD (not even proof of existence). If anyone has vendor details for
this or any other OS/2 debuggers, please either post or e-mail me,
and I will do the investigation and summarize for the net.
I am also interested in first-hand experience with any such product,
particularly with regard to usefulness and/or serious deficiencies.
Robert_S
--
Robert Stanley UUCP: uunet!mitel!cunews!cognos!roberts | 3755 Riverside Drive
Cognos, Inc. INet: roberts%cognos.uucp@ccs.carleton.ca | PO Box 9707, Ottawa
(Research) Alice: (613) 738-1338 x6115 (EST/EDT) | Ont K1G 3Z4, Canada
[I haven't really lost my mind, I'm sure I have a backup on tape somewhere.]GD.SAR@forsythe.stanford.edu (Sandy Rockowitz) (03/24/91)
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