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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8c54bb73b6fd8d22 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: GDB Woes Continued... Date: 1998/02/04 Message-ID: #1/1 X-Deja-AN: 322190714 References: <98020309134734@psavax.pwfl.com> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 886647204 27416 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-02-04T00:00:00+00:00 List-Id: Marin said << Although I don't use gdb that much, I still think it's handy - especially when you end up with an error during elaboration & don't get a traceback to know what module caused the trouble. Gdb is pretty good at filling that gap. I'd have to agree that there is a bit of a dearth of good documentation, but with what's >> Opinions about documentation can always differ, but I trust that Marin has a copy of the GDB manual from the FSF (this is available either online, or in nice printed form, either from FSF, or at your favorite technical bookstore). This is an important source of basic information on the facilities in GDB. The information on Ada mode is certainly not complete (because Ada mode is very new, and under continuing development), so there you have to rely on the documentation that comes with GNAT. It is also the case that the documentation for the GUI interface (GDBTK) is also incomplete, although, in the tradition of GUI's, the idea is that it is supposed to be easy to use without documentation :-) Still we are busy generating more comprehensive documentation for the GUI features. Robert Dewar Ada Core Technologies