From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: hardware watchpoints in non-stop - "moribund"/delayed watchpoint traps
Date: Wed, 18 Nov 2009 20:52:00 -0000 [thread overview]
Message-ID: <20091118205115.GA2301@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <200911181945.50684.pedro@codesourcery.com>
On Wed, 18 Nov 2009 20:45:50 +0100, Pedro Alves wrote:
> It seems the only case that wouldn't happen is the case of the target
> keeping reporting bad SIGTRAPs repeatedly, but I'm sure those are noticeable
> by other symptoms, like, e.g., target slowness.
Yes, I meant this case - the one which is now present in FSF GDB HEAD and
which is fixed by the hw-watchpoints patch 1/4 and which could quietly regress
one day again.
Anyway it is just a sanity check.
Regards,
Jan
next prev parent reply other threads:[~2009-11-18 20:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 14:46 Pedro Alves
2009-11-18 17:01 ` Jan Kratochvil
2009-11-18 17:51 ` Pedro Alves
2009-11-18 18:40 ` Jan Kratochvil
2009-11-18 19:46 ` Pedro Alves
2009-11-18 20:52 ` Jan Kratochvil [this message]
2009-11-20 14:15 ` Pedro Alves
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=20091118205115.GA2301@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--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