From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!mips!apple!portal!portal!cup.portal.com!Loren From: Loren@cup.portal.com (Loren Louis Hart) Newsgroups: comp.lang.ada Subject: Re: info wanted on debugging concurrent tasks Message-ID: <26889@cup.portal.com> Date: 13 Feb 90 17:38:28 GMT References: <405@wmt.UUCP> <595@ns-mx.uiowa.edu> <4722@rtech.rtech.com> <438@software.software.org> <1874@opus.cs.mcgill.ca> Organization: The Portal System (TM) List-Id: Most of the Ada debuggers are very nice, mostly because they are new and it doesn't make sense to use obsolute techniques on a new system that you are going to try to sell. The best approach for debugging multiple tasks is in a windowing environment. each task that you want to debug fires up it's own window and acts like it's own debugger. There are several systems like this, the one I am most familiar with is the Vax VMS debugger running on a Vaxstation. That particular debugger allows you to have one debugger per process. The Vax Debugger is not Ada spacific. I have also had good luck using the Verdix Debugger. I am sure I have missed some other good debuggers, but it is tough to stay current on all of them.