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 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9d3e1742bbcb99b3 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-10-12 19:24:31 PST Path: bga.com!news.sprintlink.net!howland.reston.ans.net!spool.mu.edu!sdd.hp.com!elroy.jpl.nasa.gov!lll-winken.llnl.gov!Rick.Wilson From: rick-wilson@llnl.gov (Rick Wilson) Newsgroups: comp.lang.ada Subject: Re: Ada DEC Ada for Alpha Computers Date: 11 Oct 1994 19:35:54 GMT Organization: LLNL Sender: -Not-Authenticated-[4574] Message-ID: <37epeq$kts@lll-winken.llnl.gov> References: <1994Sep15.121515.24609@sei.cmu.edu> <35af4b$g6@info.epfl.ch> NNTP-Posting-Host: rixmac.llnl.gov X-Posted-From: InterNews 1.0@lll-winken.llnl.gov. Xdisclaimer: No attempt was made to authenticate the sender's name. Date: 1994-10-11T19:35:54+00:00 List-Id: I see an important difference between debugging tasking problems and debugging multi-tasking applications. I agree with your point that you need analysis to debug tasking problems. However, I have a lot of experience working with applications containing many dozens of tasks, and I wish our debugger would handle a statement like "SET a breakpoint when task x calls routine y." This, I think, is a shortcoming of all of our APSEs. We mostly use DEC's VAX and Alpha compilers/debuggers, and while not bad, could be much better (the Alpha one in particular is a bit of a pain).