From: Pedro Alves <palves@redhat.com>
To: Iain Buclaw <ibuclaw@gdcproject.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb: Use puts_unfiltered instead of printf_unfiltered
Date: Tue, 26 Nov 2019 20:25:00 -0000 [thread overview]
Message-ID: <d1f3bf52-f88d-cce5-aeea-ea67db0d2f87@redhat.com> (raw)
In-Reply-To: <Bp1z1H0Uk-JcW1j7NMWgeijH4pFLAM5zyY6-OMDHyXwIBLc_qKy0LFyx15VMcg6gEd4IKqxbhN1mBXE5Hd0jY0U9qZj0-Poz4hQHHoYlKDc=@gdcproject.org>
On 11/26/19 12:49 PM, Iain Buclaw wrote:
> The significance of this is that printf_unfiltered writes messages to wrap_buffer, whereas puts_unfiltered pushes them immediately to stdout, resulting in "post-" messages being printed out of order.
It sounds quite surprising that two _unfiltered functions could behave differently
like that. That sounds like a bug that should be fixed, instead of worked around
by having to recall to use printf vs puts.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-11-26 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 12:49 Iain Buclaw
2019-11-26 20:13 ` Christian Biesinger via gdb-patches
2019-11-26 20:25 ` Pedro Alves [this message]
2019-11-26 23:00 ` Iain Buclaw
2020-01-17 17:57 ` Joel Brobecker
2020-01-18 18:53 ` Iain Buclaw
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=d1f3bf52-f88d-cce5-aeea-ea67db0d2f87@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.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