From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: emi-suzuki@tjsys.co.jp (Emi SUZUKI)
Cc: jan.kratochvil@redhat.com, luisgpm@linux.vnet.ibm.com,
gdb-patches@sourceware.org
Subject: Re: [RFC] "single step" atomic instruction sequences as a whole on PPC
Date: Thu, 10 May 2007 21:31:00 -0000 [thread overview]
Message-ID: <200705102130.l4ALUrjf017717@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070510.195725.01365398.emi-suzuki@tjsys.co.jp> from "Emi SUZUKI" at May 10, 2007 07:57:25 PM
Hello Emi-san,
> When that multiple SIGTRAP events occured, GDB selects one event and
> cancels the other if the cause of SIGTRAP is a breakpoint hit, or just
> leave it pended. The procedure will be done by `cancel_breakpoints_callback'
> in linux-nat.c. And the pended events will be deteced and noticed
> when the next time the target resumes.
>
> The probrem is that GDB doesn't check if the breakpoint is inserted
> for software single stepping when cancelling the trap event: when the
> event occured by a software single step breakpoint is not selected,
> GDB would not cancel it but leave it pended.
This is cancel_breakpoints_callback in linux-nat.c, right?
> When the next time the target resumes, GDB restores the pended event.
> But if you have removed the watchpoint that the target get stopped by
> before resuming, GDB can never decide the cause of SIGTRAP anymore.
> The session log above shows the phenomenon.
This looks just like a problem we fixed for the combined debugger;
cancel_breakpoints_callback should cancel SIGTRAP events caused by
software single-step breakpoints just the same as those caused by
other breakpoints.
Can you try whether the following patch fixes the problem for you?
Bye,
Ulrich
ChangeLog:
* breakpoint.c (single_step_breakpoint_inserted_here_p): New function.
* breakpoint.h (single_step_breakpoint_inserted_here_p): New prototype.
* linux-nat.c (cancel_breakpoints_callback): Treat software single-
step breakpoints the same way as regular software breakpoints.
diff -urNp gdb-orig/gdb/breakpoint.c gdb-head/gdb/breakpoint.c
--- gdb-orig/gdb/breakpoint.c 2007-05-08 14:37:32.000000000 +0200
+++ gdb-head/gdb/breakpoint.c 2007-05-10 22:34:36.776868666 +0200
@@ -7951,6 +7951,21 @@ remove_single_step_breakpoints (void)
}
}
+int
+single_step_breakpoint_inserted_here_p (CORE_ADDR pc)
+{
+ int i;
+
+ for (i = 0; i < 2; i++)
+ {
+ struct bp_target_info *bp_tgt = single_step_breakpoints[i];
+ if (bp_tgt && bp_tgt->placed_address == pc)
+ return 1;
+ }
+
+ return 0;
+}
+
\f
/* This help string is used for the break, hbreak, tbreak and thbreak commands.
It is defined as a macro to prevent duplication.
diff -urNp gdb-orig/gdb/breakpoint.h gdb-head/gdb/breakpoint.h
--- gdb-orig/gdb/breakpoint.h 2007-04-13 19:13:45.000000000 +0200
+++ gdb-head/gdb/breakpoint.h 2007-05-10 22:34:36.829861036 +0200
@@ -832,6 +832,8 @@ extern int remove_hw_watchpoints (void);
twice before remove is called. */
extern void insert_single_step_breakpoint (CORE_ADDR);
extern void remove_single_step_breakpoints (void);
+extern int single_step_breakpoint_inserted_here_p (CORE_ADDR pc);
+
/* Manage manual breakpoints, separate from the normal chain of
breakpoints. These functions are used in murky target-specific
diff -urNp gdb-orig/gdb/linux-nat.c gdb-head/gdb/linux-nat.c
--- gdb-orig/gdb/linux-nat.c 2007-05-07 02:18:12.000000000 +0200
+++ gdb-head/gdb/linux-nat.c 2007-05-10 22:34:36.860856573 +0200
@@ -1765,21 +1765,26 @@ cancel_breakpoints_callback (struct lwp_
tripped on it. */
if (lp->status != 0
- && WIFSTOPPED (lp->status) && WSTOPSIG (lp->status) == SIGTRAP
- && breakpoint_inserted_here_p (read_pc_pid (lp->ptid) -
- DECR_PC_AFTER_BREAK))
+ && WIFSTOPPED (lp->status) && WSTOPSIG (lp->status) == SIGTRAP)
{
- if (debug_linux_nat)
- fprintf_unfiltered (gdb_stdlog,
- "CBC: Push back breakpoint for %s\n",
- target_pid_to_str (lp->ptid));
+ CORE_ADDR break_pc;
+ break_pc = read_pc_pid (lp->ptid) - DECR_PC_AFTER_BREAK;
- /* Back up the PC if necessary. */
- if (DECR_PC_AFTER_BREAK)
- write_pc_pid (read_pc_pid (lp->ptid) - DECR_PC_AFTER_BREAK, lp->ptid);
+ if (breakpoint_inserted_here_p (break_pc)
+ || single_step_breakpoint_inserted_here_p (break_pc))
+ {
+ if (debug_linux_nat)
+ fprintf_unfiltered (gdb_stdlog,
+ "CBC: Push back breakpoint for %s\n",
+ target_pid_to_str (lp->ptid));
- /* Throw away the SIGTRAP. */
- lp->status = 0;
+ /* Back up the PC if necessary. */
+ if (DECR_PC_AFTER_BREAK)
+ write_pc_pid (break_pc, lp->ptid);
+
+ /* Throw away the SIGTRAP. */
+ lp->status = 0;
+ }
}
return 0;
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-05-10 21:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1177964763.15264.45.camel@localhost>
2007-05-02 14:08 ` uweigand
2007-05-03 14:51 ` Luis Machado
2007-05-06 21:20 ` Ulrich Weigand
2007-05-07 15:14 ` Luis Machado
2007-05-07 18:11 ` Ulrich Weigand
2007-05-07 19:28 ` Luis Machado
2007-05-07 22:47 ` Ulrich Weigand
2007-05-07 23:23 ` Luis Machado
2007-05-08 12:50 ` Ulrich Weigand
2007-05-09 14:33 ` Ulrich Weigand
2007-05-09 18:05 ` Luis Machado
2007-05-09 18:12 ` Daniel Jacobowitz
2007-05-09 18:21 ` Luis Machado
2007-05-09 18:34 ` Jan Kratochvil
2007-05-09 18:46 ` Daniel Jacobowitz
2007-05-09 19:10 ` Ulrich Weigand
2007-05-09 19:14 ` Luis Machado
2007-05-10 10:57 ` Emi SUZUKI
2007-05-10 21:31 ` Ulrich Weigand [this message]
2007-05-10 21:36 ` Daniel Jacobowitz
2007-05-10 22:58 ` Ulrich Weigand
2007-05-10 23:25 ` Daniel Jacobowitz
2007-05-11 7:34 ` Emi SUZUKI
2007-05-11 12:46 ` Ulrich Weigand
2007-05-09 19:45 ` Ulrich Weigand
2007-05-10 0:48 ` Luis Machado
2007-05-10 20:29 ` Ulrich Weigand
2007-04-09 2:13 Patch for gdb build on hppa hp-ux Daniel Jacobowitz
2007-04-09 23:25 ` Steve Ellcey
2007-04-10 12:05 ` Daniel Jacobowitz
2007-04-10 19:03 ` Eli Zaretskii
2007-04-10 20:22 ` Daniel Jacobowitz
2007-04-13 14:04 ` Daniel Jacobowitz
2007-04-13 17:07 ` [patch] "single step" atomic instruction sequences as a whole on PPC Luis Machado
2007-04-28 23:34 ` [RFC] " Luis Machado
2007-04-28 23:45 ` Ulrich Weigand
2007-04-29 1:53 ` Luis Machado
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=200705102130.l4ALUrjf017717@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=emi-suzuki@tjsys.co.jp \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=luisgpm@linux.vnet.ibm.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