From: KARTHIKVENKATESH BHAT <kv.bhat@samsung.com>
To: Pedro Alves <palves@redhat.com>, Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Re: [PATCH] Fix for incorect breakpoint set in case of clang compiled binary
Date: Wed, 21 Nov 2012 15:39:00 -0000 [thread overview]
Message-ID: <32244670.52091353512361480.JavaMail.weblogic@epml02> (raw)
Thanks Pedro/Mark. Appologies for the build break. I'm a bit new to GDB community will take care of it from next time.
I have fixed the warning resulting in error and modified the indentation -
Let me also try to explain the fix a bit more.
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.14849
diff -u -p -r1.14849 ChangeLog
--- ChangeLog 21 Nov 2012 14:09:03 -0000 1.14849
+++ ChangeLog 21 Nov 2012 15:11:47 -0000
@@ -1,3 +1,9 @@
+2012-11-20 Karthik Bhat <kv.bhat@samsung.com>
+
+ * i386-tdep.c (i386_skip_prologue): See if we
+ can determine the end of the prologue via the symbol table.
+ If so use the same instead of going through prologue instructions.
+
2012-11-21 Yao Qi <yao@codesourcery.com>
PR tdep/7438
Index: i386-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/i386-tdep.c,v
retrieving revision 1.364
diff -u -p -r1.364 i386-tdep.c
--- i386-tdep.c 21 Nov 2012 14:09:10 -0000 1.364
+++ i386-tdep.c 21 Nov 2012 15:11:48 -0000
@@ -1582,6 +1582,27 @@ i386_skip_prologue (struct gdbarch *gdba
CORE_ADDR pc;
gdb_byte op;
int i;
+ CORE_ADDR func_addr;
+
+ if (find_pc_partial_function (start_pc, NULL, &func_addr, NULL))
+ {
+ CORE_ADDR post_prologue_pc
+ = skip_prologue_using_sal (gdbarch, func_addr);
+ struct symtab *s = find_pc_symtab (func_addr);
+
+ /* GCC and clang always emits a line note before the prologue and another
+ one after, even if the two are at the same address or on the
+ same line. Take advantage of this so that we do not need to
+ know every instruction that might appear in the prologue. We
+ will have producer information for most binaries; if it is
+ missing (e.g. for -gstabs), assuming the GNU tools. */
+ if (post_prologue_pc
+ && (s == NULL
+ || s->producer == NULL
+ || strncmp (s->producer, "GNU ", sizeof ("GNU ") - 1) == 0
+ || strncmp (s->producer, "clang ", sizeof ("clang ") - 1) == 0))
+ return max (start_pc, post_prologue_pc);
+ }
cache.locals = -1;
pc = i386_analyze_prologue (gdbarch, start_pc, 0xffffffff, &cache);
I wanted to add this patch in GDB to fix a problem which we are currently facing when we use gdb with binary compiled with clang.
The problem faced is clang generates function prologue which is a bit different from that of GCC as a result when we try to skip prologue instruction by instruction it results in incorrect prologue_end.
There is one more method to skip prologue which is used in other architectures such as ARM(arm-tdep.c), MIPS(mips-tdep.c) etc. In this method we try to determine prologue end via symbol table.
If we are unable to do this we then we examine instruction to determine prologue end.
Added the same for i386. Here we are trying to see if we can resolve prologue end from symbol table.
This will avoid instruction by instruction examining to determine prologue end if we are able to determine it through symbol table.
Thanks
------- Original Message -------
Sender : Pedro Alves<palves@redhat.com>
Date : Nov 21, 2012 23:10 (GMT+09:00)
Title : Re: [PATCH] Fix for incorect breakpoint set in case of clang compiled binary
On 11/21/2012 01:20 PM, Mark Kettenis wrote:
> Please back it out.
Since this breaking the build I went ahead and reverted it.
--
Pedro Alves
next reply other threads:[~2012-11-21 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 15:39 KARTHIKVENKATESH BHAT [this message]
2012-11-21 15:53 ` Pedro Alves
2012-11-27 11:14 ` Mark Kettenis
-- strict thread matches above, loose matches on Subject: below --
2012-12-04 6:09 KARTHIKVENKATESH BHAT
2012-11-28 5:14 KARTHIKVENKATESH BHAT
2012-11-27 13:47 KARTHIKVENKATESH BHAT
2012-11-20 4:58 KARTHIKVENKATESH BHAT
2012-11-19 15:19 KARTHIKVENKATESH BHAT
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=32244670.52091353512361480.JavaMail.weblogic@epml02 \
--to=kv.bhat@samsung.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=palves@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