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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,392a654c4e778943 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!195.92.193.196.MISMATCH!nntp.theplanet.net!inewsm1.nntp.theplanet.net!newsfeed.icl.net!newsfeed.fjserv.net!peer-uk.news.demon.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Debugger for GNAT Date: Fri, 18 Nov 2005 22:47:15 +0000 Organization: Pushface Message-ID: References: <1132317809.937986.140480@g49g2000cwa.googlegroups.com> NNTP-Posting-Host: pogner.demon.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.demon.co.uk 1132354036 26883 62.49.19.209 (18 Nov 2005 22:47:16 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Fri, 18 Nov 2005 22:47:16 +0000 (UTC) Cancel-Lock: sha1:tYh/D72jAm9LLBxbqWJTiv5SQEA= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (darwin) Xref: g2news1.google.com comp.lang.ada:6472 Date: 2005-11-18T22:47:15+00:00 List-Id: "markp" writes: > We are currently using the GPS debugger for our GNAT Ada applications. > We feel it is not a very robust debugger, although that could be our > limited experience with it. For example, we would to be able to break > on any exceptions and view the offending line in the debugger and trace > to the source. Also, we would like to be able to set breakpoints in > tasks while the program is running without stopping everything, i.e. > stopping a single task. I don't see how your problem with breaking on exceptions can be said to make the debugger not _robust_. To set breakpoints on all exceptions via menus, try Debug / Initialize / your_program, then Debug / Data / Edit breakpoints and go to the Exception tab, then immediately click on the Add button at top right -- this selects all exceptions. If I remember correctly you could also type eg Constraint_Error where it starts off saying 'All exceptions'. Under VxWorks the recommended method of debugging indeed stops just the current task while the rest of the system trundles on. Not always the most convenient thing to happen, and you can't just skip over to another task to see what it's up to. I believe that most conventional OSs stop the whole program.