This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: MIPS stack tracing
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: Don Bowman <don at sandvine dot com>, ''Stan Shebs' ' <shebs at apple dot com>,''Greg McGary' ' <greg at mcgary dot org>,"'gdb at sources dot redhat dot com '" <gdb at sources dot redhat dot com>,"'echristo at redhat dot com '" <echristo at redhat dot com>
- Date: Sun, 03 Feb 2002 13:23:20 -0500
- Subject: Re: MIPS stack tracing
- References: <FE045D4D9F7AED4CBFF1B3B813C853371BC1CF@mail.sandvine.com> <20020203111126.A15978@nevyn.them.org>
> Also, from scanning the sources, I would have to guess that the
>> alpha architecture is suffering the same problem.
>
>
> Perhaps, perhaps not. It depends whether Alpha still uses .mdebug.
>
> .mdebug is the ECOFF/Third-Eye debugging info format; binutils recently
> switched to generating stabs-in-ELF like other targets instead.
>
> To my complete surprise, we apparently get PDR information out of the
> .mdebug section. This is somewhat bizarre, as it is also present in a
> .pdr section independent of data format. We need to read in this
> information. I'll investigate next week (if no one beats me to it :).
It would go back to SGI (Hmm, didn't sgi switch to dwarf2?) which was
using mdebug info. A number of embedded MIPS toolchains would have been
mdebug for compatability (I know this as I filed gdb/150, gdb/152 and
gdb/149) and I have a sinking feeling that they haven't yet ``just gone
away''.
Andrew