Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sourceware.org
Subject: Re: Frame lost after 'leave' and before 'ret' instruction on i386?
Date: Fri, 23 May 2008 17:23:00 -0000	[thread overview]
Message-ID: <1211479573.3601.84.camel@localhost.localdomain> (raw)
In-Reply-To: <48358860.5010703@qnx.com>

On Thu, 2008-05-22 at 10:51 -0400, Aleksandar Ristovski wrote:
> 
> So from what I can see, they all rely on symbol info (find_pc_partial_function).
> 
> Apparently I am missing something: if I were to write an "in_function_epilogue_p" 
> for i386, why would I need the debug info? As a minimum, I want to
> check if we are at one of 'ret' instructions - no debug info needed.

We've never given the same level of attention to epilogues as we
have for prologues.  I'm not aware of anyone ever having added an
epilogue disassembler a la 'scan_prologue'.

If you wanted to do that -- typically for scan_prologue, we check
to see if we have enough symbol info first, and only resort to
instruction parsing if we have to.




  parent reply	other threads:[~2008-05-22 18:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 15:32 Aleksandar Ristovski
2008-05-16 15:58 ` Daniel Jacobowitz
2008-05-16 16:02   ` Aleksandar Ristovski
2008-05-16 16:09     ` Daniel Jacobowitz
2008-05-22 14:29   ` Aleksandar Ristovski
2008-05-22 14:40     ` Aleksandar Ristovski
2008-05-22 14:50     ` Daniel Jacobowitz
2008-05-22 15:05       ` Aleksandar Ristovski
2008-05-22 16:00         ` Aleksandar Ristovski
2008-05-22 16:02         ` Daniel Jacobowitz
2008-05-23 15:19           ` Aleksandar Ristovski
2008-05-22 18:06             ` Aleksandar Ristovski
2008-05-23 17:11             ` Daniel Jacobowitz
2008-05-23 17:23         ` Michael Snyder [this message]
2008-05-26 23:08           ` Aleksandar Ristovski
2008-05-27 21:33             ` Aleksandar Ristovski
2008-05-29  6:21             ` Thiago Jung Bauermann
2008-05-29  6:22               ` Aleksandar Ristovski
2008-06-04 13:12             ` Aleksandar Ristovski
2008-06-05 20:12               ` Mark Kettenis
2008-05-16 17:24 ` Mark Kettenis
2008-05-16 17:28   ` Aleksandar Ristovski
2008-05-16 17:47     ` Daniel Jacobowitz
2008-05-16 17:48     ` Mark Kettenis

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=1211479573.3601.84.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=aristovski@qnx.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.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