From: Bernhard Heckel <bernhard.heckel@intel.com>
To: qiyaoltc@gmail.com
Cc: gdb-patches@sourceware.org, Bernhard Heckel <bernhard.heckel@intel.com>
Subject: [PATCH] AMD64, Prologue: Recognize stack decrementation as prologue operation.
Date: Thu, 01 Dec 2016 14:17:00 -0000 [thread overview]
Message-ID: <1480601804-3128-1-git-send-email-bernhard.heckel@intel.com> (raw)
Some compiler decrement stack pointer within the prologue
sequence in order to reserve memory for local variables.
Recognize this subtraction to stop at the very end of the
prologue.
2016-10-20 Bernhard Heckel <bernhard.heckel@intel.com>
gdb/Changelog:
amd64-tdep.c (amd64_analyze_prologue): Recognize stack decrementation
as prologue operation.
---
gdb/amd64-tdep.c | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/gdb/amd64-tdep.c b/gdb/amd64-tdep.c
index a3a1fde..795d78e 100644
--- a/gdb/amd64-tdep.c
+++ b/gdb/amd64-tdep.c
@@ -2283,6 +2283,12 @@ amd64_analyze_prologue (struct gdbarch *gdbarch,
/* Ditto for movl %esp, %ebp. */
static const gdb_byte mov_esp_ebp_1[2] = { 0x89, 0xe5 };
static const gdb_byte mov_esp_ebp_2[2] = { 0x8b, 0xec };
+ /* Ditto for subtraction on the stack pointer. */
+ static const gdb_byte sub_rsp_imm8[3] = { 0x48, 0x83, 0xec };
+ static const gdb_byte sub_rsp_imm32[3] = { 0x48, 0x81, 0xec };
+ /* Ditto for subtraction on the stack pointer. */
+ static const gdb_byte sub_esp_imm8[2] = { 0x83, 0xec };
+ static const gdb_byte sub_esp_imm32[2] = { 0x81, 0xec };
gdb_byte buf[3];
gdb_byte op;
@@ -2316,6 +2322,18 @@ amd64_analyze_prologue (struct gdbarch *gdbarch,
{
/* OK, we actually have a frame. */
cache->frameless_p = 0;
+
+ /* Some compiler do subtraction on the stack pointer
+ to reserve memory for local variables.
+ Two common variants exist to do so. */
+ read_code (pc + 4, buf, 3);
+ if (memcmp (buf, sub_rsp_imm8, 3) == 0)
+ /* Operand is 1 byte. */
+ return pc + 8;
+ else if (memcmp (buf, sub_rsp_imm32, 3) == 0)
+ /* Operand is 4 bytes. */
+ return pc + 11;
+
return pc + 4;
}
@@ -2327,6 +2345,18 @@ amd64_analyze_prologue (struct gdbarch *gdbarch,
{
/* OK, we actually have a frame. */
cache->frameless_p = 0;
+
+ /* Some compiler do subtraction on the stack pointer
+ to reserve memory for local variables.
+ Two common variants exist to do so. */
+ read_code (pc + 3, buf, 2);
+ if (memcmp (buf, sub_esp_imm8, 2) == 0)
+ /* Operand is 1 byte. */
+ return pc + 6;
+ else if (memcmp (buf, sub_esp_imm32, 2) == 0)
+ /* Operand is 4 bytes. */
+ return pc + 9;
+
return pc + 3;
}
}
--
2.7.1.339.g0233b80
next reply other threads:[~2016-12-01 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 14:17 Bernhard Heckel [this message]
2016-12-01 15:32 ` Luis Machado
2016-12-02 8:40 ` Bernhard Heckel
2016-12-02 15:19 ` Luis Machado
2016-12-02 23:06 ` Yao Qi
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=1480601804-3128-1-git-send-email-bernhard.heckel@intel.com \
--to=bernhard.heckel@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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