From: Eli Zaretskii <eliz@gnu.org>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA-v2] Fix a windows bug if two watchpoints are used
Date: Thu, 04 Jun 2009 07:12:00 -0000 [thread overview]
Message-ID: <E1MC77b-0001Ke-Vo@fencepost.gnu.org> (raw)
In-Reply-To: <000001c9e4de$6e550cb0$4aff2610$@u-strasbg.fr> (muller@ics.u-strasbg.fr)
> From: "Pierre Muller" <muller@ics.u-strasbg.fr>
> Cc: <gdb-patches@sourceware.org>
> Date: Thu, 4 Jun 2009 08:33:52 +0200
> Content-Language: en-us
>
> Considering the objections to my first patch, I
> here submit another patch that
> make i386_stopped_data_address
> return as soon as one hit is found.
This part is fine with me.
> The change in I386_DR_DISABLE is still
> useful for the second test inside the i386_stopped_data_address
> function.
What do we need that for? Does the Intel spec say that these its need
to be zeroed for disabled debug registers?
> This patch does fix my windows specific problem.
Is your problem fixed without the change in I386_DR_DISABLE?
next prev parent reply other threads:[~2009-06-04 7:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 22:58 [RFA] " Pierre Muller
2009-06-03 23:21 ` Eli Zaretskii
2009-06-03 23:33 ` Pierre Muller
2009-06-04 3:16 ` Eli Zaretskii
2009-06-04 3:29 ` Christopher Faylor
2009-06-04 6:34 ` [RFA-v2] " Pierre Muller
2009-06-04 7:12 ` Eli Zaretskii [this message]
2009-06-04 7:33 ` Pierre Muller
2009-06-04 10:31 ` Eli Zaretskii
2009-06-04 14:52 ` Pierre Muller
2009-06-04 15:22 ` Eli Zaretskii
2009-06-16 22:43 ` [PING][RFA-v2] " Pierre Muller
2009-06-22 20:56 ` Joel Brobecker
2009-06-23 1:04 ` Eli Zaretskii
2009-09-22 12:55 ` [RFA-v3] " Pierre Muller
2009-09-24 3:04 ` Eli Zaretskii
2009-09-24 17:54 ` Joel Brobecker
2009-09-24 22:08 ` Pierre Muller
2009-09-25 1:53 ` Joel Brobecker
2009-09-25 15:32 ` Pierre Muller
2009-09-25 16:07 ` Joel Brobecker
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=E1MC77b-0001Ke-Vo@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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