From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: schwab@suse.de
Cc: gdb@sourceware.org
Subject: Re: How to avoid stepping inside libpthread
Date: Thu, 12 Jul 2007 06:31:00 -0000 [thread overview]
Message-ID: <20070712.153049.37530505.nemoto@toshiba-tops.co.jp> (raw)
In-Reply-To: <20070712.111540.126572286.nemoto@toshiba-tops.co.jp>
On Thu, 12 Jul 2007 11:15:40 +0900 (JST), Atsushi Nemoto <anemo@mba.ocn.ne.jp> wrote:
> > See deal_with_atomic_sequence in rs6000-tdep.c, which tries to solve the
> > same issue.
>
> Thank you. I'll try to implement the feature for mips.
Thanks, it worked. Here is a patch against gdb-6.6.
I'll port this patch to current gdb, but while it seems current gdb
cannot find libpthread symbol, another test code (or fixing gdb) would
be needed first ...
--- gdb-6.6.org/gdb/mips-tdep.c 2006-08-09 06:32:37.000000000 +0900
+++ gdb-6.6/gdb/mips-tdep.c 2007-07-12 14:11:46.000000000 +0900
@@ -2177,6 +2177,86 @@ mips_addr_bits_remove (CORE_ADDR addr)
return addr;
}
+/* Instruction masks used during single-stepping of atomic sequences. */
+#define LLSC_MASK 0xfc000000
+#define LL_INSTRUCTION 0xc0000000
+#define LLD_INSTRUCTION 0xd0000000
+#define SC_INSTRUCTION 0xe0000000
+#define SCD_INSTRUCTION 0xf0000000
+
+/* Checks for an atomic sequence of instructions beginning with a LL/LLD
+ instruction and ending with a SC/SCD instruction. If such a sequence
+ is found, attempt to step through it. A breakpoint is placed at the end of
+ the sequence. */
+
+static int
+deal_with_atomic_sequence (CORE_ADDR pc)
+{
+ CORE_ADDR breaks[2] = {-1, -1};
+ CORE_ADDR loc = pc;
+ CORE_ADDR branch_bp; /* Breakpoint at branch instruction's destination. */
+ int insn;
+ int insn_count;
+ int index;
+ int last_breakpoint = 0; /* Defaults to 0 (no breakpoints placed). */
+ const int atomic_sequence_length = 16; /* Instruction sequence length. */
+
+ if (pc & 0x01)
+ return 0;
+
+ insn = mips_fetch_instruction (loc);
+ /* Assume all atomic sequences start with a ll/lld instruction. */
+ if ((insn & LLSC_MASK) != LL_INSTRUCTION
+ && (insn & LLSC_MASK) != LLD_INSTRUCTION)
+ return 0;
+
+ /* Assume that no atomic sequence is longer than "atomic_sequence_length"
+ instructions. */
+ for (insn_count = 0; insn_count < atomic_sequence_length; ++insn_count)
+ {
+ loc += MIPS_INSN32_SIZE;
+ insn = mips_fetch_instruction (loc);
+
+ /* Assume that there is at most one branch in the atomic
+ sequence. If a branch is found, put a breakpoint in its
+ destination address. */
+ branch_bp = mips_next_pc (loc);
+ if (branch_bp != loc + MIPS_INSN32_SIZE)
+ {
+ if (last_breakpoint >= 1)
+ return 0; /* More than one branch found, fallback to the
+ standard single-step code. */
+ breaks[1] = branch_bp;
+ last_breakpoint++;
+ }
+
+ if ((insn & LLSC_MASK) == SC_INSTRUCTION
+ || (insn & LLSC_MASK) == SCD_INSTRUCTION)
+ break;
+ }
+
+ /* Assume that the atomic sequence ends with a sc/scd instruction. */
+ if ((insn & LLSC_MASK) != SC_INSTRUCTION
+ && (insn & LLSC_MASK) != SCD_INSTRUCTION)
+ return 0;
+
+ loc += MIPS_INSN32_SIZE;
+
+ /* Insert a breakpoint right after the end of the atomic sequence. */
+ breaks[0] = loc;
+
+ /* Check for duplicated breakpoints. Check also for a breakpoint
+ placed (branch instruction's destination) in the atomic sequence */
+ if (last_breakpoint && pc <= breaks[1] && breaks[1] <= breaks[0])
+ last_breakpoint = 0;
+
+ /* Effectively inserts the breakpoints. */
+ for (index = 0; index <= last_breakpoint; index++)
+ insert_single_step_breakpoint (breaks[index]);
+
+ return 1;
+}
+
/* mips_software_single_step() is called just before we want to resume
the inferior, if we want to single-step it but there is no hardware
or kernel single-step support (MIPS on GNU/Linux for example). We find
@@ -2193,6 +2273,9 @@ mips_software_single_step (enum target_s
if (insert_breakpoints_p)
{
pc = read_register (mips_regnum (current_gdbarch)->pc);
+ if (deal_with_atomic_sequence (pc))
+ return;
+
next_pc = mips_next_pc (pc);
insert_single_step_breakpoint (next_pc);
next prev parent reply other threads:[~2007-07-12 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 6:18 Atsushi Nemoto
2007-07-11 9:00 ` Andreas Schwab
2007-07-12 2:15 ` Atsushi Nemoto
2007-07-12 6:31 ` Atsushi Nemoto [this message]
2007-07-12 11:10 ` Daniel Jacobowitz
2007-07-13 7:04 ` Atsushi Nemoto
2007-09-26 21:06 ` Daniel Jacobowitz
2007-07-11 11:40 ` 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=20070712.153049.37530505.nemoto@toshiba-tops.co.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=gdb@sourceware.org \
--cc=schwab@suse.de \
/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