Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Use dwarf2 unwinding on ARM
Date: Tue, 29 Mar 2005 15:47:00 -0000	[thread overview]
Message-ID: <1112111179.12337.9.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <20050325211209.GA2461@nevyn.them.org>

On Fri, 2005-03-25 at 21:12, Daniel Jacobowitz wrote:
> Hi Richard,
> 
> We talked last year about turning on dwarf2-based unwinding for ARM.  The
> problem was that older versions of GCC would emit incorrect unwind
> information for Thumb functions, but that's been fixed for a while
> now; I think it's time to throw the switch in GDB.
> 
> Committed to csl-arm-20050325-branch.  OK for HEAD?

I'd forgotten that we hadn't.  Yes, this is ok for head too.

R.


  reply	other threads:[~2005-03-29 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-25 21:11 Daniel Jacobowitz
2005-03-29 15:47 ` Richard Earnshaw [this message]
2005-03-29 16:56   ` 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=1112111179.12337.9.camel@pc960.cambridge.arm.com \
    --to=rearnsha@gcc.gnu.org \
    --cc=drow@false.org \
    --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