From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: The threads saga: watchpoints
Date: Fri, 07 Mar 2003 14:22:00 -0000 [thread overview]
Message-ID: <20030307142230.GA20634@nevyn.them.org> (raw)
It was pointed out to me today that watchpoints and threads really don't get
along. It's even in the manual:
_Warning:_ In multi-thread programs, watchpoints have only limited
usefulness. With the current watchpoint implementation, GDB can
only watch the value of an expression _in a single thread_. If
you are confident that the expression can only change due to the
current thread's activity (and if you are also confident that no
other thread can become current), then you can use watchpoints as
usual. However, GDB may not notice when a non-current thread's
activity changes the expression.
I think some of our hardware breakpoint implementations have the same issue.
It seems to me that, in general, this should be pretty easy to fix. But it
requires some definite changes in the current infrastructure. Shouldn't we
be able to insert the watchpoint in all threads?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2003-03-07 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 14:22 Daniel Jacobowitz [this message]
2003-03-07 14:37 ` Elena Zannoni
2003-03-07 14:43 ` 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=20030307142230.GA20634@nevyn.them.org \
--to=drow@mvista.com \
--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