From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 0/4] Fix hw watchpoints
Date: Tue, 18 Aug 2009 16:34:00 -0000 [thread overview]
Message-ID: <e394668d0908180924t5d933abfwaf6632e40a60cb9a@mail.gmail.com> (raw)
In-Reply-To: <20090817194531.GA10694@host0.dyn.jankratochvil.net>
On Mon, Aug 17, 2009 at 12:45 PM, Jan
Kratochvil<jan.kratochvil@redhat.com> wrote:
> Hi,
>
> hw watchpoints currently have multiple issues for various corner cases, such
> as false hits, hits shown by SIGTRAP with no watchpoint printed, crashing
> forked processes, hanging fork etc.
>
> Regression tested only as a whole patchset on:
> x86_64-fedora11-linux-gnu
> x86_64-fedora11-linux-gnu -m32
> i686-fedora11-linux-gnu
> ppc64-rhel52-linux-gnu
> with default ppc target, no regressions but some new FAILs which are
> not caused by the new code in these patches
> ia64-rhel53-linux-gnu
> no regressions, new FAIL ("hbreak") which is not caused by the new
> code in these patches
> s390x-rhel53-linux-gnu
> with default s390x target, no regressions, new FAILs, "reorder" is
> some pthreads/kernel bug or incompatibility, "watchpoints-hw" is not
> caused by the new code in these patches (did not analyze more)
>
> Patches are incrementally dependent on each other. Expecting to check-in all
> of them together, their dependencies may not be strictly incremental. The GDB
> looks basically OK / tests OK on their incremental application (for testing).
>
> While the non-stop mode was regression tested by the GDB testsuite I did not
> consider much how the changes affect it. I think some of the fixes are not
> needed for non-stop.
>
>
> Thanks,
> Jan
>
Hi. Have you looked at whether gdbserver has similar issues?
next prev parent reply other threads:[~2009-08-18 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 19:45 Jan Kratochvil
2009-08-18 16:34 ` Doug Evans [this message]
2009-08-18 17:10 ` Jan Kratochvil
2009-08-18 21:23 ` Doug Evans
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=e394668d0908180924t5d933abfwaf6632e40a60cb9a@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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