From: Jiong Wang <jiwang@tilera.com>
To: <gdb-patches@sourceware.org>
Cc: Walter Lee <walt@tilera.com>
Subject: [RFC/TileGX 2/6] simplify the handling of skip prologue for plt stub
Date: Fri, 18 Jan 2013 09:25:00 -0000 [thread overview]
Message-ID: <50F91516.6010204@tilera.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 290 bytes --]
for tilegx, when skip prologue, if the start_pc is a plt stub address, then
stop to go further, just return the start_pc.
gdb/ChangeLog:
* tilegx-tdep.c (tilegx_skip_prologue): simplify the handling for
plt stub.
please review.
---
Regards,
Jiong
Tilera Corporation.
[-- Attachment #2: 0003-fix-plt-stub-issue.patch --]
[-- Type: text/x-patch, Size: 575 bytes --]
---
gdb/tilegx-tdep.c | 4 ++++
1 files changed, 4 insertions(+)
diff --git a/gdb/tilegx-tdep.c b/gdb/tilegx-tdep.c
index 2f1d824..6432edb 100644
--- a/gdb/tilegx-tdep.c
+++ b/gdb/tilegx-tdep.c
@@ -746,6 +746,10 @@ tilegx_skip_prologue (struct gdbarch *gdbarch, CORE_ADDR pc)
return sal.end;
}
+ /* for plt stub, just return the start pc */
+ if (in_plt_section (pc, NULL))
+ return pc;
+
/* Otherwise, try to skip prologue the hard way. */
return tilegx_analyze_prologue (gdbarch,
pc, pc + 8 * TILEGX_BUNDLE_SIZE_IN_BYTES,
--
1.7.10.3
next reply other threads:[~2013-01-18 9:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 9:25 Jiong Wang [this message]
2013-01-18 13:15 ` Joel Brobecker
2013-01-18 15:12 ` Jiong Wang
2013-01-18 17:30 ` Pedro Alves
2013-02-15 3:22 ` Jiong Wang
2013-02-16 4:50 ` Yao Qi
2013-02-20 2:49 ` Jiong Wang
2013-02-20 4:11 ` Yao Qi
2013-02-21 13:40 ` Jiong Wang
2013-03-01 10:35 ` Jiong Wang
2013-03-01 11:31 ` Pedro Alves
2013-03-01 14:08 ` Jiong Wang
2013-03-01 15:59 ` Pedro Alves
2013-03-02 1:40 ` [COMMITTED][RFC/TileGX " Jiong Wang
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=50F91516.6010204@tilera.com \
--to=jiwang@tilera.com \
--cc=gdb-patches@sourceware.org \
--cc=walt@tilera.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