This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: GDB on SGI Irix 6.5
- To: davea at quasar dot engr dot sgi dot com
- Subject: Re: GDB on SGI Irix 6.5
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- Date: Wed, 13 Jun 2001 21:38:09 +0300
- CC: ac131313 at cygnus dot com, gdb at sources dot redhat dot com
- References: <200106131650.JAA27856@quasar.engr.sgi.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Wed, 13 Jun 2001 09:50:09 -0700 (PDT)
> From: David B Anderson <davea@quasar.engr.sgi.com>
>
> The irix 64 dwarf2 debug info is identical
> to what dwarf2read.c reads (and only dwarf2read, not anything else)
> except for the initial bytes of CU being 8 bytes, not 12
> (see dwarf2read) and the determination of offset and length
> size being based on 'IRIX6.5' not on internal evidence in the dwarf
> itself.
So you are saying that there's nothing in the file--not a single
thing--that would allow GDB to find out if the debug info is for 64 or
n32 ABI?
Would it be reasonable then to try one format, and if that fails, try
the other? (I know that it fails somewhere, because when I try to
debug a 64-bit executable with GDB built from current CVS, it
complains about something like ``wrong version'' (IIRC).)