From: Eli Zaretskii <eliz@gnu.org>
To: Cleber Rosa <crosa@redhat.com>
Cc: gdb-patches@sourceware.org, crosa@redhat.com, areis@redhat.com
Subject: Re: [PATCH v2 2/3] GDBServer: introduce --server-output command line option
Date: Wed, 25 Mar 2015 20:55:00 -0000 [thread overview]
Message-ID: <83iodool02.fsf@gnu.org> (raw)
In-Reply-To: <1427316472-20629-3-git-send-email-crosa@redhat.com>
> From: Cleber Rosa <crosa@redhat.com>
> Cc: crosa@redhat.com, areis@redhat.com
> Date: Wed, 25 Mar 2015 17:47:51 -0300
>
> This command line option will redirect all of the gdbserver's own
> output (always sent to stderr) to a separate file. This feature makes
> it possible to distinguish between the inferior process stderr and
> gdbserver's own stderr. Example use case:
>
> $ gdbserver --server-output=log :2222 bin >bin.out 2>bin.err
>
> Server output will be sent to file named "log", and the inferior
> output and error messages will be on files "bin.out" and "bin.err",
> respectively.
>
> gdb/Changelog:
> 2015-03-25 Cleber Rosa <crosa@redhat.com>
>
> * NEWS: New feature in the GDBserver: --server-output.
>
> gdb/doc/ChangeLog:
> 2015-03-25 Cleber Rosa <crosa@redhat.com>
>
> * gdb.texinfo (info): Added section on command line and monitor
> commands.
> (gdbserver man): Added section on new command line option.
OK for the documentation parts, with one comment:
> +Server output will be sent to file named @var{log}, and the inferior
> +output and error messages will be on files @var{bin.out} and
> +@var{bin.err}, respectively.
These all should be @file, not @var, since they are literal file
names.
Thanks.
next prev parent reply other threads:[~2015-03-25 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 20:48 [PATCH v2 0/3] GDBServer: introduce a dedicated output stream Cleber Rosa
2015-03-25 20:48 ` [PATCH v2 2/3] GDBServer: introduce --server-output command line option Cleber Rosa
2015-03-25 20:55 ` Eli Zaretskii [this message]
2015-03-25 21:08 ` Cleber Rosa
2015-03-25 20:48 ` [PATCH v2 1/3] GDBServer: introduce a stream dedicated to the server Cleber Rosa
2015-03-25 20:48 ` [PATCH v2 3/3] GDBServer: add 'monitor set server-output' command Cleber Rosa
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=83iodool02.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=areis@redhat.com \
--cc=crosa@redhat.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).