From: Daniel Jacobowitz <drow@false.org>
To: Emi SUZUKI <emi-suzuki@tjsys.co.jp>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [RFA] thread specific breakpoints and single stepping
Date: Sat, 26 Jul 2008 03:02:00 -0000 [thread overview]
Message-ID: <20080726030133.GC1895@caradoc.them.org> (raw)
In-Reply-To: <20080709.211038.135588294.emi-suzuki@tjsys.co.jp>
On Wed, Jul 09, 2008 at 09:10:38PM +0900, Emi SUZUKI wrote:
> It works better than mine. But while I am concerning about
> single-stepping for software watchpoints, I noticed that we should
> also check whether a hardware watchpoint is triggered.
As this condition gets more complicated, I'm getting worried about
keeping it in sync with everything else. Could it be that the logic
is wrong - we should determine whether a thread hop is necessary later
in the process? It should be just like a breakpoint with a false
condition.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-07-26 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 2:49 Ems SUZUKI
2008-07-08 20:05 ` Pedro Alves
2008-07-09 12:15 ` Emi SUZUKI
2008-07-26 3:02 ` Daniel Jacobowitz [this message]
2008-08-01 12:00 ` Emi SUZUKI
2008-08-19 6:10 ` SUZUKI Emi
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=20080726030133.GC1895@caradoc.them.org \
--to=drow@false.org \
--cc=emi-suzuki@tjsys.co.jp \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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