Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 24 Apr 2014 09:57:44 -0700
From: Isaac Dunham <>
Subject: looking at fmtmsg-is dprintf oom-safe?

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.

Isaac Dunham

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.