Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb@sources.redhat.com
Subject: Re: Frame lost after 'leave' and before 'ret' instruction on i386?
Date: Wed, 04 Jun 2008 13:12:00 -0000	[thread overview]
Message-ID: <g264bk$5bo$1@ger.gmane.org> (raw)
In-Reply-To: <4836E0A7.8050800@qnx.com>

Any comments on this? 

Aleksandar Ristovski wrote:
> Hello,
> The patch is an attempt to solve the issue from the subject. It 
> introduces a check for in_function_epilogue_p and introduces 
> architecture level prev_register_from_epilogue.
> 
> The patch is a draft (works but is not complete).
> Rationale: Dealing with epilogue in frame unwinders needs to be done 
> only in sentinel frame (older frames will never be in epilogue).
> Comments appreciated.
> 
> 
> Thanks,
> 
> Aleksandar Ristovski
> QNX Software Systems
> 
> 
> ChangeLog (for reference only):
> 
>     * gdbarch.c, gdbarch.h: Regenerated.
>     * gdbarch.sh: Introduce gdbarch_prev_frame_from_epilogue and provide
>     default_prev_frame_from_epilogue.
>     * i386-tdep.c (i386_in_function_epilogue_p, 
>     i386_prev_register_from_epilogue): New functions.
>     (struct frame_unwind_cache): Struct definition.
>     (i386_gdbarch_init): Register i386_prev_register_from_epilogue and
>     i386_in_function_epilogue_p.
>     * sentinel-frame.c (sentinel_frame_prev_register): Check if we are
>     in epilogue and if so, call gdbarch provided prev_frame_from_epilogue.
>     If this returns NULL do as before.
> 



  parent reply	other threads:[~2008-06-04 13:12 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
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 [this message]
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='g264bk$5bo$1@ger.gmane.org' \
    --to=aristovski@qnx.com \
    --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