From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Add possibility to force buffering mode for stdout/stderr
Date: Wed, 21 Aug 2013 17:26:00 -0000 [thread overview]
Message-ID: <000f01ce9e93$88620770$99261650$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <83ppt7jb2f.fsf@gnu.org>
Hi Eli,
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : mercredi 21 août 2013 17:52
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC] Add possibility to force buffering mode for
stdout/stderr
>
> > From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> > Date: Wed, 21 Aug 2013 17:08:29 +0200
> >
> > This patch add
> > setvbuf wrapping inside ui_file structure.
> >
> > This maintenance feature is
> > to allow to test the effect of
> > changing the buffering mode on the testsuite output.
> >
> > basically adding
> > "-ex {maint setvbuf stdout full 1000000}"
> > or
> > "-ex {maint setvbuf stdout line 80}"
> > should allow to test both performance differences
> > induced by buffering changes and possible regressions
> > in testsuite results.
>
> Thanks.
>
> Please also document this command in the manual.
Where should I add information about such a feature...
as it is only useful for developers,
it's probably better to put it into gdbint.texinfo, no?
But I found no obvious place where to put such information...
I need your help here!
Pierre
next prev parent reply other threads:[~2013-08-21 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"001201ce9e80$4b90b3e0$e2b21ba0$@muller"@ics-cnrs.unistra.fr>
2013-08-21 15:51 ` Eli Zaretskii
2013-08-21 17:26 ` Pierre Muller [this message]
[not found] ` <"000f01ce9e93$88620770$99261650$@muller"@ics-cnrs.unistra.fr>
2013-08-21 17:58 ` Eli Zaretskii
2013-08-21 15:08 Pierre Muller
2013-08-25 1:08 ` Yao Qi
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='000f01ce9e93$88620770$99261650$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=eliz@gnu.org \
--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