This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: huge remote debug traffic with multi-thread program
- From: Mark Kettenis <kettenis at gnu dot org>
- To: anemo at mba dot ocn dot ne dot jp
- Cc: gdb at sources dot redhat dot com, drow at false dot org
- Date: Thu, 17 Mar 2005 19:20:53 +0100 (CET)
- Subject: Re: huge remote debug traffic with multi-thread program
- References: <20050217.104200.93020045.nemoto@toshiba-tops.co.jp><20050218.193333.07644163.nemoto@toshiba-tops.co.jp><20050222.164614.84976901.nemoto@toshiba-tops.co.jp> <20050317.144338.51867419.nemoto@toshiba-tops.co.jp>
Date: Thu, 17 Mar 2005 14:43:38 +0900 (JST)
From: Atsushi Nemoto <anemo@mba.ocn.ne.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.
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. */
Sorry, missed your first post when travelling. I had the same patch
in my tree for OpenBSD/mips64 support. There are some problems with
the mips_single_step_through_delay though, and I intended to solve
those first. However, this doesn't make matters worse, so I've
checked it in.
Thanks,
Mark