From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Vladimir Prus'" <vladimir@codesourcery.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: RE: [RFA] Clarify infrun variable naming.
Date: Fri, 23 Nov 2007 16:14:00 -0000 [thread overview]
Message-ID: <006101c82deb$e62d1da0$b28758e0$@u-strasbg.fr> (raw)
In-Reply-To: <200711231851.47586.vladimir@codesourcery.com>
> Yes. What I mean is that there are two situations now:
>
> 1. When we step over breakpoint, we disable everything, including
> watchpoints.
> 2. When we hit watchpoint, and the PC is at the instruction itself, we
> disable
> all breakpoints and watchpoints when stepping.
>
> (2) might not be a problem now, but if we wish to interact with one
> thread,
> while others are running, it might become a problem -- other threads
> might miss unrelated breakpoints and watchpoints. So, we need to:
>
> - Remove breakpoints at current PC
> - Remove watchpoint a the address being accessed
> - Single step
>
> I suspect you was more interested in (1), but that's basically two
> sides
> of the coin.
Yes, but this scheme should indeed also work to resolve the
watchpoint miss of gdb/38.
About Daniel's answer, suggesting to use thread specific
watchpoints, I don't know if thread specific
watchpoints are available on all archs... Which would mean
that both schemes need to be implemented.
Pierre
next prev parent reply other threads:[~2007-11-23 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 13:23 Vladimir Prus
2007-11-23 14:53 ` Pierre Muller
2007-11-23 15:22 ` Vladimir Prus
2007-11-23 15:41 ` Pierre Muller
2007-11-23 15:51 ` Vladimir Prus
2007-11-23 16:06 ` Daniel Jacobowitz
2007-11-23 17:03 ` Vladimir Prus
2007-11-23 17:27 ` Daniel Jacobowitz
2007-11-23 16:14 ` Pierre Muller [this message]
2007-12-05 1:18 ` Jim Blandy
2007-12-05 1:52 ` Daniel Jacobowitz
2007-12-05 2:47 ` Daniel Jacobowitz
2007-12-05 8:37 ` Vladimir Prus
2007-12-05 14:13 ` Vladimir Prus
2007-12-05 21:32 ` Jim Blandy
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='006101c82deb$e62d1da0$b28758e0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@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