From: Pedro Alves <palves@redhat.com>
To: Christian Biesinger <cbiesinger@google.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Replace the remaining uses of strerror with safe_strerror
Date: Fri, 06 Dec 2019 20:06:00 -0000 [thread overview]
Message-ID: <ddc204c8-8353-f230-97f5-a6de9a6ba0b2@redhat.com> (raw)
In-Reply-To: <20191126195901.50696-1-cbiesinger@google.com>
On 11/26/19 7:59 PM, Christian Biesinger via gdb-patches wrote:
> index c37db579f7..724a1d24db 100644
> --- a/gdb/gdbsupport/safe-strerror.c
> +++ b/gdb/gdbsupport/safe-strerror.c
> @@ -27,11 +27,18 @@ safe_strerror (int errnum)
> {
> static thread_local char buf[1024];
>
> +#ifdef IN_PROCESS_AGENT
> + /* IPA does not use Gnulib, but only supports Linux, so we can safely
> + call the GNU version of strerror_r here. It is documented not to
> + return NULL. */
> + return strerror_r (errnum, buf, sizeof (buf));
GDBserver and (I assume) the IPA can be built with other C runtimes on Linux,
like musl and others. Do you know how musl behaves?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-12-06 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 19:59 Christian Biesinger via gdb-patches
2019-11-26 21:11 ` [PATCH v2] " Christian Biesinger via gdb-patches
2019-12-06 20:06 ` Pedro Alves [this message]
2019-12-06 20:36 ` [PATCH] " Christian Biesinger via gdb-patches
2019-12-06 20:44 ` [PATCH v3] " Christian Biesinger via gdb-patches
2019-12-06 21:46 ` [PATCH] " Pedro Alves
2019-12-09 19:11 ` Christian Biesinger via gdb-patches
2019-12-09 19:13 ` [PATCH v3] " Christian Biesinger via gdb-patches
2019-12-10 16:41 ` Pedro Alves
2019-12-10 19:25 ` Christian Biesinger via gdb-patches
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=ddc204c8-8353-f230-97f5-a6de9a6ba0b2@redhat.com \
--to=palves@redhat.com \
--cc=cbiesinger@google.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