From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: RE: [RFA] gdbserver: also issue remote debug information for getpkt in no-ack-mode
Date: Sat, 14 Feb 2009 00:23:00 -0000 [thread overview]
Message-ID: <000801c98e38$6b098ab0$411ca010$@u-strasbg.fr> (raw)
In-Reply-To: <200902132348.59402.pedro@codesourcery.com>
Thanks, Pedro,
I committed the patch without that spurious empty line.
Pierre Muller
Pascal language support maintainer for GDB
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pedro Alves
> Envoyé : Saturday, February 14, 2009 12:49 AM
> À : gdb-patches@sourceware.org
> Cc : Pierre Muller
> Objet : Re: [RFA] gdbserver: also issue remote debug information for
> getpkt in no-ack-mode
>
> On Monday 09 February 2009 16:04:08, Pierre Muller wrote:
>
> > Is this OK?
>
> Looks good to me (tiny comment in the patch below). I thought I
> had already fixed this in HEAD, but I see the fix done in
> the multi-process branch only. :-)
>
> > Could someone tell me how to setup a
> > dejagnu target to run the testsuite
> > with cygwin gdbserver on a cygwin machine?
>
> See here:
>
> http://sourceware.org/gdb/wiki/Native_gdbserver_testing
>
> This works on Cygwin, as I use this method there.
>
> > + else
> > + {
> > + if (remote_debug)
> > + {
> > + fprintf (stderr, "getpkt (\"%s\"); [no ack sent] \n", buf);
> > + fflush (stderr);
> > + }
> > +
>
> Spurious blank line here.
>
> > + }
> >
>
> --
> Pedro Alves
next prev parent reply other threads:[~2009-02-14 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 16:04 Pierre Muller
2009-02-13 23:53 ` Pedro Alves
2009-02-14 0:23 ` Pierre Muller [this message]
2009-02-14 6:39 ` 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='000801c98e38$6b098ab0$411ca010$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--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