From: Daniel Jacobowitz <drow@false.org>
To: Steve Freeland <caucasatron@yahoo.ca>
Cc: gdb@sources.redhat.com
Subject: Re: Watchpoints in multithreaded programs
Date: Sun, 01 Oct 2006 23:24:00 -0000 [thread overview]
Message-ID: <20061001232443.GA12735@nevyn.them.org> (raw)
In-Reply-To: <20061001212327.86189.qmail@web34208.mail.mud.yahoo.com>
On Sun, Oct 01, 2006 at 02:23:27PM -0700, Steve Freeland wrote:
> So... I'm a bit confused. Is the manual out of date? Did the
> "watchthreads" patch never make it into mainline builds for some
> reason?
It never did. Discussion trailed off and we never heard anything else
about it from the submitter.
I recall seeing a few weeks ago that there is an updated version in
the Red Hat SRPMs. Could any of the list subscribers from Red Hat
comment - is that version fit for submission?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-01 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 21:23 Steve Freeland
2006-10-01 23:24 ` Daniel Jacobowitz [this message]
2007-04-25 20:37 ` Jan Kratochvil
2006-10-03 3:53 Steve Freeland
2006-10-03 4:07 ` 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=20061001232443.GA12735@nevyn.them.org \
--to=drow@false.org \
--cc=caucasatron@yahoo.ca \
--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