From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 3/4] Fix hw watchpoints: remove dead code [update]
Date: Wed, 07 Oct 2009 18:51:00 -0000 [thread overview]
Message-ID: <20091007185110.GS5689@adacore.com> (raw)
In-Reply-To: <20091003171059.GC26203@host0.dyn.jankratochvil.net>
> 2009-08-17 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * i386-nat.c (i386_stopped_by_hwbp): Remove.
Thanks for taking care of that. From what I can tell, this function
has never been used ever since it was introduced in 2001! (for everyone's
interest, if you are wondering why we like git so much, git log -p --grep
gave me that answer within a couple of minutes:).
> gdb/testsuite/
> 2009-10-03 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.base/watchpoint-hw.exp: New variable breakline.
> (hbreak, continue to break-at-exit after hbreak): New tests.
This part is approved. The issue is that the testcase is dependent
on another patch which is still pending. You can either merge that
patch into the one it depends on, but I'd rather have a separate
small testcase for hbreak. That way, if hbreak alone breaks, we
only have to look at that, rather than start by isolating the hbreak
problem from the rest of the testcase.
--
Joel
next prev parent reply other threads:[~2009-10-07 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 19:46 [patch 3/4] Fix hw watchpoints: remove dead code Jan Kratochvil
2009-10-03 17:11 ` [patch 3/4] Fix hw watchpoints: remove dead code [update] Jan Kratochvil
2009-10-07 18:51 ` Joel Brobecker [this message]
2009-10-07 19:28 ` Joel Brobecker
2009-10-07 19:40 ` Jan Kratochvil
2009-10-07 19:55 ` Jan Kratochvil
2009-10-07 21:51 ` Joel Brobecker
2009-10-08 13:10 ` Jan Kratochvil
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=20091007185110.GS5689@adacore.com \
--to=brobecker@adacore.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