From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, pmuldoon@redhat.com
Subject: Re: [PATCH v2 9/9] compile: compile printf: gdbserver support
Date: Sat, 11 Apr 2015 19:31:00 -0000 [thread overview]
Message-ID: <83iod2ea2r.fsf@gnu.org> (raw)
In-Reply-To: <20150411192324.GA27879@host1.jankratochvil.net>
> Date: Sat, 11 Apr 2015 21:23:24 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org, pmuldoon@redhat.com
>
> On Mon, 06 Apr 2015 19:43:22 +0200, Eli Zaretskii wrote:
> > > --- a/gdb/doc/gdb.texinfo
> > > +++ b/gdb/doc/gdb.texinfo
> > > @@ -17246,7 +17246,9 @@ multiple-line editor.
> > > @item compile printf @var{template}, @var{expressions}@dots{}
> > > Compile and execute @code{printf} function call with the compiler
> > > language found as the current language in @value{GDBN}
> > > -(@pxref{Languages}).
> > > +(@pxref{Languages}). Inferior executes @code{open_memstream} and
> > > +@code{fprintf} instead so that the produced string is printed by
> > > +@value{GDBN} and not the inferior.
> >
> > Is this really important to say in the manual?
> >
> > And if it is, why not simply say that the value is printed by GDB
> > itself, not by calling functions in the inferior?
>
> Used:
> The value is printed by @value{GDBN} and not the inferior, inferior
> does not execute specifically the function @code{printf}.
Fine with me, thanks.
next prev parent reply other threads:[~2015-04-11 19:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 17:26 [PATCH v2 0/9] compile: compile print&printf Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 4/9] compile: Support relocation to GNU-IFUNCs Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 1/9] Code cleanup: Make parts of print_command_1 public Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 2/9] compile: Distribute scope, add scope_data Jan Kratochvil
2015-04-06 17:26 ` [PATCH v2 3/9] Code cleanup: compile: Constify some parameters Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 7/9] compile: New 'compile print' Jan Kratochvil
2015-04-06 17:41 ` Eli Zaretskii
2015-04-06 17:49 ` Paul_Koning
2015-04-06 17:52 ` Jan Kratochvil
2015-04-06 18:00 ` Paul_Koning
2015-04-08 20:03 ` Jan Kratochvil
2015-04-09 7:39 ` Eli Zaretskii
2015-04-09 17:40 ` [doc patch] compile: missing bits [Re: [PATCH v2 7/9] compile: New 'compile print'] Jan Kratochvil
2015-04-09 18:12 ` Eli Zaretskii
2015-04-10 8:09 ` Jan Kratochvil
2015-04-10 8:31 ` Eli Zaretskii
2015-04-10 8:35 ` [commit] " Jan Kratochvil
2015-04-10 14:09 ` Paul_Koning
2015-04-08 20:12 ` [PATCH v2 7/9] compile: New 'compile print' Paul_Koning
2015-04-08 20:33 ` Jan Kratochvil
2015-04-06 18:47 ` Jan Kratochvil
2015-04-11 19:20 ` Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 5/9] compile: Use -Wall, not -w Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 9/9] compile: compile printf: gdbserver support Jan Kratochvil
2015-04-06 17:43 ` Eli Zaretskii
2015-04-11 19:23 ` Jan Kratochvil
2015-04-11 19:31 ` Eli Zaretskii [this message]
2015-04-06 17:27 ` [PATCH v2 6/9] Code cleanup: compile: func_addr -> func_sym Jan Kratochvil
2015-04-06 17:27 ` [PATCH v2 8/9] compile: New compile printf Jan Kratochvil
2015-04-11 19:46 ` obsolete: [PATCH v2 0/9] compile: compile print&printf Jan Kratochvil
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=83iod2ea2r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pmuldoon@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).