Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Orjan Friberg <orjan.friberg@axis.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Dwarf-2 unwinding vs. manual prologue analysis
Date: Fri, 27 May 2005 09:26:00 -0000	[thread overview]
Message-ID: <4296E7B8.9080504@axis.com> (raw)
In-Reply-To: <20050526150841.GA9804@nevyn.them.org>

Daniel Jacobowitz wrote:
> Please use gdb@ for questions; I expect most messages to gdb-patches to
> be in need of review :-)

Sorry about that.  Fixed (even though I guess it might break the threading).

> On Thu, May 26, 2005 at 04:59:05PM +0200, Orjan Friberg wrote:
>>
>>Do I need to able to do manual prologue analysis when there's Dwarf-2 CFI 
>>available?  If so, is there a set of minimum requirements for what that 
>>analysis must be able figure out?
> 
> 
> No.  If enabling the DWARF-2 CFI support causes things to break, then
> you need to inspect your CFI; it is probably broken.  

I'm not sure I understand what you mean.  Are you saying that the CFI might be 
broken if the manual prologue analysis is used in cases where the Dwarf-2 CFI 
should be available (and sufficient)?  Since I don't have a correct prologue 
scanner for CRISv32, nothing would work without having the Dwarf-2 frame sniffer 
hooked in.

> You need to do
> prologue analysis if there's anything without CFI that you need to
> handle, which there usually is - for instance PLT stubs.

Ok, I'll look into that.  Thanks.

-- 
Orjan Friberg
Axis Communications


       reply	other threads:[~2005-05-27  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4295E439.7070104@axis.com>
     [not found] ` <20050526150841.GA9804@nevyn.them.org>
2005-05-27  9:26   ` Orjan Friberg [this message]
2005-05-27 10:43   ` Orjan Friberg

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=4296E7B8.9080504@axis.com \
    --to=orjan.friberg@axis.com \
    --cc=drow@false.org \
    --cc=gdb@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