From: Florian Weimer <fw@deneb.enyo.de>
To: Leo Liang <ycliang@andestech.com>
Cc: <libc-help@sourceware.org>, <peterlin@andestech.com>,
<dylan@andestech.com>, <alankao@andestech.com>
Subject: Re: Is it reasonable to expect errno to be 0 when entering main?
Date: Tue, 27 Sep 2022 09:31:49 +0200 [thread overview]
Message-ID: <87edvxz316.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <YzKjAMjPIywq7tvI@ubuntu01> (Leo Liang's message of "Tue, 27 Sep 2022 07:15:12 +0000")
* Leo Liang:
> Besides, Do you have any suggestion as to how this could be fixed?
> We could try send out a patch as well!
Hiding the getrandom failure is probably sufficient. All other
failures in malloc will lead to the process failing to start, so those
errors don't need to be masked.
prev parent reply other threads:[~2022-09-27 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 12:07 Leo Liang
2022-09-27 6:05 ` Florian Weimer
2022-09-27 7:15 ` Leo Liang
2022-09-27 7:31 ` Florian Weimer [this message]
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=87edvxz316.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=alankao@andestech.com \
--cc=dylan@andestech.com \
--cc=libc-help@sourceware.org \
--cc=peterlin@andestech.com \
--cc=ycliang@andestech.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).