From: Kyle McMartin <kmcmarti@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] aarch64: skip over stack protector setup in function prologues
Date: Tue, 03 Jun 2014 05:00:00 -0000 [thread overview]
Message-ID: <20140603050011.GA15355@redacted.bos.redhat.com> (raw)
When debugging code which ends up with stack protector setup in the
function prologue, break points on functions end up stopping in the
prologue, instead of on a useful statement inside the function. To fix
this, do something similar to ARM (which has more cases to handle) and
analyse the instructions we stopped at to see if its the stack protector
sequence.
Also add a simple testcase to check to see if we successfully manage to
end up on the statement we expect or not. (Which could also be used as a
test on ARM, but I don't have hardware handy, will investigate later.)
regards, Kyle
gdb/aarch64-tdep.c | 125 +++++++++++++++++++--
gdb/testsuite/gdb.arch/aarch64-stack_chk_guard.c | 28 +++++
gdb/testsuite/gdb.arch/aarch64-stack_chk_guard.exp | 43 +++++++
3 files changed, 189 insertions(+), 7 deletions(-)
next reply other threads:[~2014-06-03 5:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 5:00 Kyle McMartin [this message]
2014-06-03 5:02 ` [PATCH 1/2] aarch64: extend decode_adrp to decode immediate offset Kyle McMartin
2014-06-03 8:22 ` Marcus Shawcroft
2014-06-03 14:50 ` Kyle McMartin
2014-06-03 5:03 ` [PATCH 2/2] aarch64: implement walking over the stack protector Kyle McMartin
2014-06-03 5:42 ` Andrew Pinski
2014-06-03 14:51 ` Kyle McMartin
2014-06-05 20:06 ` Kyle McMartin
2014-06-05 20:36 ` Andrew Pinski
2014-06-05 20:53 ` Kyle McMartin
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=20140603050011.GA15355@redacted.bos.redhat.com \
--to=kmcmarti@redhat.com \
--cc=gdb-patches@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