Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Richard.Earnshaw@buzzard.freeserve.co.uk
Cc: gdb-patches@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: [RFA] Repost ARM frame patches
Date: Wed, 03 Sep 2003 20:41:00 -0000	[thread overview]
Message-ID: <20030903204139.GA9605@nevyn.them.org> (raw)
In-Reply-To: <200309022252.h82MqQum001042@buzzard.buzzard.freeserve.co.uk>

On Tue, Sep 02, 2003 at 11:52:26PM +0100, Richard Earnshaw wrote:
> Daniel,
> 
> My appologies for not reviewing this before.  Just way too much day job...
> 
> It looks fine to me (at least, it seems better than what's there at 
> present).
> 
> My only question is, once we start using the dwarf2 unwinder, can it cope 
> with the fact that gcc currently does not emit frame unwind information 
> for Thumb code? (ie can it handle a mix of code that uses dwarf2 and 
> traditional unwinding?)

I was going to say yes, but...

drow@nevyn:/big/fsf/projects/arm/obj/gdb/testsuite/interwork% readelf -wf test1.o
The section .debug_frame contains:

00000000 0000000c ffffffff CIE
  Version:               1
  Augmentation:          ""
  Code alignment factor: 1
  Data alignment factor: -4
  Return address column: 14

  DW_CFA_def_cfa: r13 ofs 0

00000010 0000000c 00000000 FDE cie=00000000 pc=00000000..0000001c

00000020 0000000c 00000000 FDE cie=00000000 pc=0000001c..00000046


i.e. GCC emits _empty_ dwarf unwind information for thumb functions,
rather than none at all.  That's unlikely to work.  We'd need to modify
the dwarf2 unwinder to ignore empty FDEs.

I'll check in the non-dwarf parts now, and then we can figure out what
to do about that.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-09-03 20:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29  1:50 Daniel Jacobowitz
2003-09-02 22:56 ` Richard Earnshaw
2003-09-03 20:41   ` Daniel Jacobowitz [this message]
2003-09-05  9:50     ` Richard Earnshaw
2003-09-05 20:43       ` Andrew Cagney
2004-02-08  4:11       ` Daniel Jacobowitz
2004-02-09 12:12         ` Richard Earnshaw

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=20030903204139.GA9605@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Richard.Earnshaw@buzzard.freeserve.co.uk \
    --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