From: Vladimir Prus <ghost@cs.msu.su>
To: Johan Rydberg <jrydberg@virtutech.com>
Cc: Daniel Jacobowitz <drow@false.org>, Eli Zaretskii <eliz@gnu.org>,
gdb@sources.redhat.com
Subject: Re: read watchpoints broken with remote targets?
Date: Mon, 14 Nov 2005 08:21:00 -0000 [thread overview]
Message-ID: <200511141121.25826.ghost@cs.msu.su> (raw)
In-Reply-To: <43782D46.9050702@virtutech.com>
On Monday 14 November 2005 09:23, Johan Rydberg wrote:
> Daniel Jacobowitz wrote:
> > Actually, I think it is the right solution. [...]
> > So a watchpoint was found not to have triggered, but failed to change
> > bs->stop, so it was bogusly reported.
>
> This is exactly the change I have done in my private repo, and it seem
> to work just fine for our purposes.
Good to know you've arrived to the same fix.
Any chance this will be applied? Should Johan, or I, send the patch to
gdb-patches?
- Volodya
prev parent reply other threads:[~2005-11-14 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 13:21 Vladimir Prus
2005-11-11 17:39 ` Eli Zaretskii
2005-11-13 17:09 ` Daniel Jacobowitz
2005-11-14 6:23 ` Johan Rydberg
2005-11-14 8:21 ` Vladimir Prus [this message]
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=200511141121.25826.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jrydberg@virtutech.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).