This is the mail archive of the
mailing list for the glibc project.
Re: Do we care about malloc failure in tests?
- From: Florian Weimer <fweimer at redhat dot com>
- To: Paul Pluzhnikov <ppluzhnikov at google dot com>, GLIBC Devel <libc-alpha at sourceware dot org>, Bill Parker <wp02855 at gmail dot com>
- Date: Tue, 7 Jun 2016 18:44:40 +0200
- Subject: Re: Do we care about malloc failure in tests?
- Authentication-results: sourceware.org; auth=none
- References: <CALoOobNcJ6MaE3OfhY2KebXa=Z8kzhsgKpoesbzvvhUEEZhz=A at mail dot gmail dot com> <20160531220247 dot GC7717 at vapier dot lan> <CALoOobP0AHXDbX6qiKtpXOhwH8GY+MDVwaxfTSWakumW7+HN4Q at mail dot gmail dot com> <20160606015434 dot GG5431 at vapier dot lan>
On 06/06/2016 03:54 AM, Mike Frysinger wrote:
On 05 Jun 2016 17:39, Paul Pluzhnikov wrote:
+oom_error (const char *fn)
+ fprintf (stderr, "Out of memory in %s\n", fn);
use printf as we don't let test write to stderr anymore
might want to tweak the printf like so:
printf ("%s: allocation failed: %m\n", fn);
Perhaps also include the request allocation size as well.