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=3.4 required=5.0 tests=BAYES_50,INVALID_DATE, MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!attcan!uunet!clyde.concordia.ca!mcgill-vision!quiche!opus!clement From: clement@opus.cs.mcgill.ca (Clement Pellerin) Newsgroups: comp.lang.ada Subject: info wanted on debugging concurrent tasks Keywords: debugger, Concurrent C Message-ID: <1874@opus.cs.mcgill.ca> Date: 12 Feb 90 17:50:27 GMT References: <405@wmt.UUCP> <595@ns-mx.uiowa.edu> <4722@rtech.rtech.com> <438@software.software.org> Reply-To: clement@opus.UUCP (Clement Pellerin) Organization: SOCS, McGill University, Montreal, Canada List-Id: Debugging concurrent programs is becoming a hot research topic. I hope to adapt Ada debugger technology to Concurrent C. Since Ada programmers have been writing concurrent programs for a long time, I suspect there must be some nice debuggers out there. We might learn some lessons because for now, debugging Concurrent C programs has been near to impossible. What is the state of debugger technology for Ada? I am especially interested in "methodologies" for debugging concurrent programs, i.e some theory as to how to go about it. Once a methodology is found, a debugger can be written to support it. The theory does not have to be mathematical. So how do YOU go about debugging concurrent tasks? Is debugging tasks as hopeless as debugging concurrent C processes? I would like a small description of what your favorite debugger can do together with any reference to articles that you've seen. thank you. -- news