From: Daniel Jacobowitz <drow@mvista.com>
To: Hilfinger@CS.Berkeley.EDU
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA/mips: Use ".pdr" sections generated by GAS
Date: Thu, 13 Jun 2002 10:52:00 -0000 [thread overview]
Message-ID: <20020613175243.GA28194@nevyn.them.org> (raw)
In-Reply-To: <200206131749.KAA07048@tully.CS.Berkeley.EDU>
On Thu, Jun 13, 2002 at 10:49:07AM -0700, Paul Hilfinger wrote:
>
> > > According to its documentation, exc_unwind on IRIX 6.5 currently uses
> > > .debug_frame information for unwinding purposes (and its native
> > > assembler now does not produce PDR sections there). I am not familiar
> > > with the set of all MIPS platforms, so I am moved to ask whether it
> > > would (1) be a good idea if or (2) be unnecessary for GDB to do the
> > > same thing.
> >
> > Did the IRIX 6.5 assembler ever produce PDR sections? I was unaware of
> > this.
>
> Sorry for the confusing wording. I should have said simply that the
> IRIX assembler no longer produces PDR information. (To be honest, I
> really haven't followed the evolution of this software enough to know
> when last the SGI tool chain DID produce this information, but am
> piecing together scraps of historical data by reading out-of-date
> comments on current #include files and historical hints in current
> man pages.)
Let me clarify my response too, then... did any IRIX assembler ever
produce PDR sections? I've been unable to find any evidence of this,
but I haven't spent great effort searching.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-06-13 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 10:08 Daniel Jacobowitz
2002-06-12 16:04 ` Andrew Cagney
2002-06-13 7:16 ` Daniel Jacobowitz
2002-06-13 10:02 ` Paul Hilfinger
2002-06-13 10:32 ` Daniel Jacobowitz
2002-06-13 10:49 ` Paul Hilfinger
2002-06-13 10:52 ` Daniel Jacobowitz [this message]
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=20020613175243.GA28194@nevyn.them.org \
--to=drow@mvista.com \
--cc=Hilfinger@CS.Berkeley.EDU \
--cc=gdb-patches@sources.redhat.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