Re: GDB Woes Continued...

Re: GDB Woes Continued...

[Marin David Condic, 561.796.8997, M/S 731-96]

wanker@EXPLOITED.BARMY.ARMY writes:
>In article <6b50fl$knt@lotho.delphi.com>,  <tmoran@bix.com> wrote:
>>>deleted it from my system because there wasn't a useful debugger
>>>available.  Without being able to debug my code, ...
>>  Did your Ada system give source code walkbacks on unhandled
>>exceptions, or (in Ada 95) in Ada.Exceptions.Exception_Information?
>>I find *much* less usage of the debugger now that I have those.
>
>Unfortunately, it did not give me any sort of walkback.
>

    If you are using gdb, try these instructions to get a traceback.
    It's bailed me out more than once:

    Instructions for getting the Gnat Debugger to do a stack dump
    (traceback) when some crash is occurring.

    1) Compile and link with debug options set.

        gnatmake -f -g <main unit> -largs g

    2) Run program with GDB as documentation indicates.

        gdb <program name>

    (gdb) break __gnat_unhandled_exception
    (gdb) run
    (gdb) backtrace
    (gdb) quit


    Good luck with it...

    MDC

Marin David Condic, Senior Computer Engineer     Voice:     561.796.8997
Pratt & Whitney GESP, M/S 731-95, P.O.B. 109600  Fax:       561.796.4669
West Palm Beach, FL, 33410-9600                  Internet:  CONDICMA@PWFL.COM
=============================================================================
    "I filled out an application that said, 'In Case Of Emergency
    Notify'. I wrote 'Doctor'... What's my mother going to do?"
        --  Steven Wright
=============================================================================

Re: GDB Woes Continued...

[Robert Dewar]

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

Re: GDB Woes Continued: language related ?

[Roger Racine]

In article <01bd333c$4fb8b000$452c5c8b@aptiva>, "Jerry van Dijk"
<jvandyk@ibm.net> wrote:

> What just occured to me is that contrary to Martin I use
> the Dutch language version of Win95.
> 
> Is anyone having trouble with gdb on a US Win95 ?

Yes, but I have what I am told is a rare version: Windows 3.1 => Windows
95 Upgrade that I bought in a store.  This version is supposedly fraught
with peril for gdb.

Re: GDB Woes Continued: language related ?

[Robert Dewar]

<<Yes, but I have what I am told is a rare version: Windows 3.1 => Windows
95 Upgrade that I bought in a store.  This version is supposedly fraught
with peril for gdb.
>>

That's a bit overwrought! In fact we have reports of people successfully
using the original Win95 (the one you are using) successfully, although
we are not running that ourselves. I merely suggested that it might be
one fact in the behavior differences that people see. No one said that
using the original release was necessarily "fraught with peril for gdb".

Robert Dewar
Ada Core Technologies

P.S. you might want to go about upgrading your Win95 as far as possible
anyway. A lot of the improvements in OSR2 are available for free downloading.

Re: GDB Woes Continued: language related ?

[Jerry van Dijk]

> BTW, the problem isn't GDB per se, but the Borland C runtime that is
> used by the TK and TCL DLLs that it uses.

Now that's an interesting tidbit, as I have both MS and Borland C++
installed
on my systems...

-- 
-- Jerry van Dijk | Leiden, Holland
-- Team Ada       | email: jdijk@acm.org

Re: GDB Woes Continued: language related ?

[Richard Kenner]

In article <rracine-0902980655220001@rjr1287.draper.com> rracine@draper.com (Roger Racine) writes:
>Yes, but I have what I am told is a rare version: Windows 3.1 => Windows
>95 Upgrade that I bought in a store.  This version is supposedly fraught
>with peril for gdb.

Download and install the "Service release 1" and some of its bugfixes
from Microsoft and install.  That's a worthwhile thing to do anyway
and I've run GDB on such a system with no problem.

BTW, the problem isn't GDB per se, but the Borland C runtime that is
used by the TK and TCL DLLs that it uses.