From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Don Bowman <don@sandvine.com>, ''Stan Shebs' ' <shebs@apple.com>,
''Greg McGary' ' <greg@mcgary.org>,
gdb@sources.redhat.com
Subject: Re: MIPS stack tracing
Date: Sun, 03 Feb 2002 12:29:00 -0000 [thread overview]
Message-ID: <3C5D9D9B.2010409@cygnus.com> (raw)
In-Reply-To: <20020203151308.A22013@nevyn.them.org>
> 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''.
>
>
> Is gdb/150 still valid? I thought I remembered that being fixed. But
> if it is, I may take a potshot at it.
Yes :-(
I suspect extracting teath from a wodden hen or even the dwarf2 changes
JimB outlined are easier tasks ... :-) Remember it is extra_*func*_info
and not extra_*frame*_info. Grep for mips_extra_func_info in the
*ALPHA* sources.
And yes, that bag in the pocket in front of you is there for a reason.
Andrew
next prev parent reply other threads:[~2002-02-03 20:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 12:29 Don Bowman
2002-02-03 12:29 ` Daniel Jacobowitz
2002-02-03 12:29 ` Andrew Cagney
2002-02-03 12:13 ` Daniel Jacobowitz
2002-02-03 12:29 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-07 6:56 Don Bowman
2002-02-07 7:30 ` Daniel Jacobowitz
2002-02-06 9:40 Don Bowman
2002-02-06 16:45 ` Daniel Jacobowitz
2002-02-04 9:22 David Anderson
2002-02-03 15:49 Don Bowman
2002-02-02 12:14 Don Bowman
2002-02-02 14:45 ` Daniel Jacobowitz
2002-02-02 11:26 Don Bowman
2002-02-02 12:11 ` Stan Shebs
2002-02-02 10:58 David Anderson
2002-02-02 9:57 David Anderson
2002-02-01 10:15 Don Bowman
2002-02-01 11:32 ` Daniel Jacobowitz
2002-02-02 11:16 ` Greg McGary
2002-01-31 14:27 Don Bowman
2002-02-01 9:37 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C5D9D9B.2010409@cygnus.com \
--to=ac131313@cygnus.com \
--cc=don@sandvine.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=greg@mcgary.org \
--cc=shebs@apple.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox