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.6 required=5.0 tests=BAYES_40,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c84883971adf36e9 X-Google-Attributes: gid103376,public From: "Corey Ashford" Subject: Re: Recommendations on a debugger Date: 1998/07/29 Message-ID: <6pp4i5$1g9$1@usenet.rational.com>#1/1 X-Deja-AN: 376253820 References: <35BF762F.3CBA70E8@pica.army.mil> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Organization: Rational Software Newsgroups: comp.lang.ada Date: 1998-07-29T00:00:00+00:00 List-Id: Dennis Gross wrote in message <35BF762F.3CBA70E8@pica.army.mil>... >Can someone recommend a decent debugger "tool" for Ada running in an NT >environment. (We have been unhappy with the debugger that comes with >the Aonix Object Ada.) > >Tom McBride mcbride@pica.army.mil (or mcbridt@ix.netcom.com) > Unfortunately, a debugger has to have intimate knowledge of the way the compiler puts out debug information in order for you to be able to debug Ada code at the source level. This is due to the complexity of Ada over languages such as C and lack of standards with respect to debugging information formats. Even C++ debuggers are compiler intimate (hey.. did I coin a new phrase?). In other words, if you switch debuggers, you'll have to switch compilers too. There are several NT based Ada compilers available - GNAT, and Rational's Apex NT (plug plug) among them. - Corey