From: Isaac Dunham <ibid.ag@gmail.com>
To: musl@lists.openwall.com
Subject: looking at fmtmsg-is dprintf oom-safe?
Date: Thu, 24 Apr 2014 09:57:44 -0700 [thread overview]
Message-ID: <20140424165743.GA643@muslin> (raw)
Hello,
I've been poking at fmtmsg(), since if I added that and used sdbm for
dbm.h, I'd have XSI coverage.
Due to the use case for fmtmsg (reporting errors, including terminal
errors), I expect it needs to work even when malloc() fails.
My understanding is that this would exclude using fopen().
I could use several calls to write() (I currently have a preliminary
version that does this), but dprintf() would be more optimal.
As far as I can tell, dprintf() should still work when malloc() fails,
but I'd like to confirm this.
Thanks,
Isaac Dunham
next reply other threads:[~2014-04-24 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 16:57 Isaac Dunham [this message]
2014-04-25 14:50 ` Rich Felker
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=20140424165743.GA643@muslin \
--to=ibid.ag@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).