From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Doug Evans'" <dje@google.com>, <gdb-patches@sourceware.org>
Cc: "'Pedro Alves'" <pedro@codesourcery.com>
Subject: RE: [RFA] i386/amd64 h/w watchpoints in gdbserver
Date: Tue, 19 May 2009 09:05:00 -0000 [thread overview]
Message-ID: <001201c9d860$e66c5850$b34508f0$@u-strasbg.fr> (raw)
In-Reply-To: <e394668d0905181627ref57f83oc11507d07c0382a7@mail.gmail.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Doug Evans
> Envoyé : Tuesday, May 19, 2009 1:28 AM
> À : gdb-patches@sourceware.org; muller@ics.u-strasbg.fr
> Objet : Re: [RFA] i386/amd64 h/w watchpoints in gdbserver
>
> Oh, btw, yes I know it needs updating 'cus i386/amd64 gdbserver is now
> biarch. :-)
> That part is mechanical.
> Is there anything that still needs discussing?
Doug, I think that your should send a new RFA
for an up-to-date patch with the bi-arch stuff.
Do we have an automated testsuite result comparison script
that can be used for gdbserver testing?
I can test compilation on cygwin,
but testing can only be done manually...
Hopefully, Pedro will then be able to review it rapidly.
Pierre Muller
Pascal language support maintainer for GDB
next prev parent reply other threads:[~2009-05-19 9:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 7:19 Doug Evans
2009-05-01 8:10 ` Pierre Muller
2009-05-18 23:11 ` Doug Evans
2009-05-18 23:28 ` Doug Evans
2009-05-19 9:05 ` Pierre Muller [this message]
2009-06-02 15:36 ` Doug Evans
2009-06-02 22:47 ` Pierre Muller
2009-06-03 0:18 ` Doug Evans
2009-06-03 16:27 ` Pierre Muller
2009-06-09 3:43 ` Doug Evans
2009-06-10 5:05 ` Pierre Muller
2009-06-18 19:04 ` Doug Evans
2009-06-20 23:54 ` Pedro Alves
2009-06-23 7:37 ` Doug Evans
2009-06-29 20:45 ` Pedro Alves
2009-06-30 10:32 ` Doug Evans
2009-06-30 10:56 ` Pedro Alves
2009-06-30 15:58 ` Pierre Muller
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='001201c9d860$e66c5850$b34508f0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=dje@google.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