Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Paul Hilfinger <hilfingr@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:32:00 -0000	[thread overview]
Message-ID: <20020613173225.GA27321@nevyn.them.org> (raw)
In-Reply-To: <200206131701.KAA26726@tully.CS.Berkeley.EDU>

On Thu, Jun 13, 2002 at 10:01:42AM -0700, Paul Hilfinger wrote:
> 
> > >ECOFF debug information (mdebug) included the concept of a PDR.  MIPS uses
> > >these for unwinding through functions, among other things.  Right now we 
> > >can
> > >get them from mdebug or from code inspection.  But current GNU binutils
> > >emits ".pdr" sections instead of using the old ".mdebug" style debug info.
> 
> 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.

Yes, we should use .debug_frame (when it is available).  Dan Berlin
mentioned this a week or so ago on gcc@ also.  Most of the code is
there, it just needs to be hooked in.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-06-13 17:32 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 [this message]
2002-06-13 10:49         ` Paul Hilfinger
2002-06-13 10:52           ` 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=20020613173225.GA27321@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hilfingr@CS.Berkeley.EDU \
    /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