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.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2c0bee8a07770dd4 X-Google-Attributes: gid103376,public From: Stephen Leake Subject: Re: [Gnat] Finding exceptions without gdb Date: 1996/11/06 Message-ID: <32809DEF.665E@gsfc.nasa.gov>#1/1 X-Deja-AN: 194874279 references: content-type: text/plain; charset=us-ascii organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA mime-version: 1.0 reply-to: Stephen.Leake@gsfc.nasa.gov newsgroups: comp.lang.ada x-mailer: Mozilla 3.0 (Win95; U) Date: 1996-11-06T00:00:00+00:00 List-Id: Bob Collins wrote: > > Is there any way to find out where (in source) exceptions > are raised without using gdb? (And without Put-ting the > information in excception handlers.) Ooops, sorry for my last post. It's early, and I read the request as "how do I find exceptions USING gdb", but the question is "WITHOUT using gdb". Sigh. The only way I know to identify the point an exception is raised is to se gdb to catch it. An approximate location can be found by putting exception handlers in EVERY block, and putting a message to a screen, or passing a string in a re-raised exception. You have ruled out both options. Why have you ruled these out? -- - Stephe