From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: Jim Blandy <jimb@red-bean.com>, gdb@sources.redhat.com
Subject: Re: Argument pointers, dwarf and prologue analysis
Date: Mon, 21 Nov 2005 15:26:00 -0000 [thread overview]
Message-ID: <20051121152640.GA21540@nevyn.them.org> (raw)
In-Reply-To: <4381E376.5020003@tausq.org>
On Mon, Nov 21, 2005 at 11:10:46PM +0800, Randolph Chung wrote:
> >We've got dwarf unwind information to play with now. Even with the new
> >additions in dwarf3, it's not so good at representing what you need.
> >I'd need to see a larger example to know how we could, or couldn't, do
> >this.
>
> What would you like to see?
How about full assembly and debug info for some case we get wrong? At
least three frames where the middle one uses its arguments after the
call site, so we have a non-leaf function to look at.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-21 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 5:50 Randolph Chung
2005-11-21 7:42 ` Jim Blandy
2005-11-21 10:32 ` Randolph Chung
2005-11-21 14:08 ` Daniel Jacobowitz
2005-11-21 15:11 ` Randolph Chung
2005-11-21 15:26 ` Daniel Jacobowitz [this message]
2005-11-22 0:07 ` Randolph Chung
2005-11-22 5:15 ` Jim Blandy
2005-11-22 6:39 ` Randolph Chung
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=20051121152640.GA21540@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@red-bean.com \
--cc=randolph@tausq.org \
/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