From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: gdb@sources.redhat.com
Cc: drow@false.org
Subject: Re: huge remote debug traffic with multi-thread program
Date: Thu, 17 Mar 2005 05:43:00 -0000 [thread overview]
Message-ID: <20050317.144338.51867419.nemoto@toshiba-tops.co.jp> (raw)
In-Reply-To: <20050222.164614.84976901.nemoto@toshiba-tops.co.jp>
>>>>> On Tue, 22 Feb 2005 16:46:14 +0900 (JST), Atsushi Nemoto <anemo@mba.ocn.ne.jp> said:
anemo> This patch fixed my problem. Please review and apply if
anemo> appropriate. Thank you.
Ping. This patch add a breakpoint test which was lost on 2004-10-31
change:
> 2004-10-31 Orjan Friberg <organ.friberg@axis.com>
> Andrew Cagney <cagney@gnu.org>
>
> * gdbarch.sh (single_step_through_delay): Add.
> * gdbarch.h, gdbarch.c: Re-generate.
> * config/mips/tm-mips.h (STEP_SKIPS_DELAY_P, STEP_SKIPS_DELAY)
> (mips_step_skips_delay): Delete.
> * mips-tdep.c (mips_single_step_through_delay): Replace
> mips_step_skips_delay.
> (mips_gdbarch_init): Set single_step_through_delay.
> (mips_dump_tdep): Do not print STEP_SKIPS_DELAY.
Please review. Thank you.
--- gdb/mips-tdep.c.orig 2005-02-21 13:31:58.000000000 +0900
+++ gdb/mips-tdep.c 2005-02-22 11:45:07.159141141 +0900
@@ -4148,6 +4148,8 @@ mips_single_step_through_delay (struct g
if (mips_pc_is_mips16 (pc))
return 0;
+ if (!breakpoint_here_p (pc + 4))
+ return 0;
if (!safe_frame_unwind_memory (frame, pc, buf, sizeof buf))
/* If error reading memory, guess that it is not a delayed
branch. */
---
Atsushi Nemoto
next prev parent reply other threads:[~2005-03-17 5:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 16:24 Atsushi Nemoto
2005-02-17 1:42 ` Daniel Jacobowitz
2005-02-17 9:01 ` Atsushi Nemoto
2005-02-18 22:54 ` Atsushi Nemoto
2005-02-22 18:59 ` Atsushi Nemoto
2005-03-17 5:43 ` Atsushi Nemoto [this message]
2005-03-17 11:38 ` Bob Rossi
2005-03-17 18:21 ` Mark Kettenis
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=20050317.144338.51867419.nemoto@toshiba-tops.co.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=drow@false.org \
--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