From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: 'Eli Zaretskii' <eliz@gnu.org>,
'Mark Kettenis' <mark.kettenis@xs4all.nl>,
gdb-patches@sourceware.org
Subject: Re: [RFA-v3] Fix a windows bug if two watchpoints are used
Date: Fri, 25 Sep 2009 01:53:00 -0000 [thread overview]
Message-ID: <20090925015337.GJ2112@adacore.com> (raw)
In-Reply-To: <003f01ca3d63$607027a0$215076e0$@u-strasbg.fr>
> I only wanted to have the fix in the branch,
> I don't insist on having the new testsuite files
> in 7.0
I wouldn't worry about the testcase files, they do not impact
the debugger functionality, so they are not a big risk. The risk
is with the patch itself, so I was asking whether there was a way
you could test this on x86 before checking in the branch.
Normally, testing on one architecture is sufficient, but
I'm getting a little (too?) paranoid...
In other words, if you commit the patch, go ahead and commit
the testcase as well. It doesn't matter whether it's on the branch
or not.
--
Joel
next prev parent reply other threads:[~2009-09-25 1:53 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
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 [this message]
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=20090925015337.GJ2112@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--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