From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "Michael Snyder" <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Add epilogue unwinder for AMD64
Date: Mon, 17 Aug 2009 11:19:00 -0000 [thread overview]
Message-ID: <d959247b9f960e29c1afd333775085d1.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <4A88A1EA.8010705@vmware.com>
> This patch corresponds to the similar one in i386-tdep.c, and
> corrects for a gcc issue with elf/dwarf debug info in function
> epilogues. It is needed in order to make reverse-step and next
> work properly for stepping backward through a return.
>
> No testsuite regressions.
>
> OK to commit?
Looks ok to me.
I'm back from a 14-day trip now, so I'll try to review other pending
i386/amd64 stuff ASAP. Unfortunately my ADSL link is currently hosed so
it may take a couple of more days.
next prev parent reply other threads:[~2009-08-17 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 3:35 Michael Snyder
2009-08-17 11:19 ` Mark Kettenis [this message]
2009-08-17 18:27 ` Michael Snyder
2009-08-17 14:39 ` Hui Zhu
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=d959247b9f960e29c1afd333775085d1.squirrel@webmail.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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