From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb@sources.redhat.com
Subject: [RFC] stepping over permanent breakpoint
Date: Mon, 16 Mar 2009 17:41:00 -0000 [thread overview]
Message-ID: <gpm2v2$n1o$1@ger.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
Hello,
When there is a hard-coded breakpoint in code, like in this
example (for x86):
#include <stdio.h>
int main()
{
__asm(" int $0x03\n");
printf("Hello World\n");
return 0;
}
gdb on linux will appear to work correctly.
However, on systems that do not need pc adjustment after
break (like QNX) gdb will not be able to step over that
breakpoint unless user explicitly sets a breakpoint on top
of it.
I think that in case of linux it is actually working by
accident - because kernel does not back-up instruction
pointer after hard-coded breakpoint instruction was
executed. Gdb will receive SIGTRAP but will not really know why.
Attached patch fixes this for systems where
gdbarch_decr_pc_after_break (gdbarch) == 0
I am still not sure this is the final fix. Wouldn't it be
better if we recognized a hard-coded breakpoint as a
breakpoint? There would be an issue since it is not in the
breakpoint list, but maybe we should either automatically
add it when we encounter it, or perhaps print with some
"special" number (to make it clear to the user it is not one
of the user-generated breakpoints).
Thanks,
Aleksandar Ristovski
QNX Software Systems
ChangeLog for your reference:
* infrun.c (adjust_pc_after_break): On systems with adjusted
PC after break, make sure hard-coded breakpoint is stepped-over.
[-- Attachment #2: infrun.c-adjust_pc_after_break-permanent-breakpoints-20090316.diff --]
[-- Type: text/x-patch, Size: 1309 bytes --]
Index: gdb/infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.361
diff -u -p -r1.361 infrun.c
--- gdb/infrun.c 1 Mar 2009 23:18:36 -0000 1.361
+++ gdb/infrun.c 16 Mar 2009 17:33:22 -0000
@@ -2089,14 +2089,29 @@ adjust_pc_after_break (struct execution_
we have nothing to do. */
regcache = get_thread_regcache (ecs->ptid);
gdbarch = get_regcache_arch (regcache);
- if (gdbarch_decr_pc_after_break (gdbarch) == 0)
- return;
/* Find the location where (if we've hit a breakpoint) the
breakpoint would be. */
breakpoint_pc = regcache_read_pc (regcache)
- gdbarch_decr_pc_after_break (gdbarch);
+ if (gdbarch_decr_pc_after_break (gdbarch) == 0)
+ {
+ /* Check if we have stopped at a permanent breakpoint. */
+ int len;
+ const gdb_byte *brk;
+ gdb_byte *target_mem = alloca(32);
+
+ brk = gdbarch_breakpoint_from_pc (gdbarch, &breakpoint_pc, &len);
+ if (!target_read_memory (breakpoint_pc, target_mem, len)
+ && memcmp (target_mem, brk, len) == 0)
+ {
+ breakpoint_pc += len;
+ regcache_write_pc (regcache, breakpoint_pc);
+ }
+ return;
+ }
+
/* Check whether there actually is a software breakpoint inserted at
that location.
next reply other threads:[~2009-03-16 17:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 17:41 Aleksandar Ristovski [this message]
2009-03-16 18:22 ` Pedro Alves
2009-03-16 18:55 ` Aleksandar Ristovski
2009-03-16 19:38 ` Pedro Alves
2009-03-16 20:37 ` Aleksandar Ristovski
2009-03-16 18:50 ` Mark Kettenis
2009-03-16 19:04 ` Aleksandar Ristovski
2009-03-23 16:50 ` RFC: Program Breakpoints (was: [RFC] stepping over permanent breakpoint) Ross Morley
2009-03-24 16:57 ` Daniel Jacobowitz
2009-03-24 20:33 ` RFC: Program Breakpoints Ross Morley
2009-03-24 20:40 ` Daniel Jacobowitz
2009-03-24 23:48 ` Pedro Alves
2009-03-25 7:58 ` Mark Kettenis
2009-03-25 13:17 ` Pedro Alves
2009-03-24 23:59 ` Ross Morley
2009-03-31 0:44 ` Ross Morley
2009-03-31 3:17 ` Daniel Jacobowitz
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='gpm2v2$n1o$1@ger.gmane.org' \
--to=aristovski@qnx.com \
--cc=gdb@sources.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