This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Do we care about malloc failure in tests?

From: Mike Frysinger <vapier at gentoo dot org>
To: Paul Pluzhnikov <ppluzhnikov at google dot com>
Cc: GLIBC Devel <libc-alpha at sourceware dot org>, Bill Parker <wp02855 at gmail dot com>
Date: Sun, 5 Jun 2016 21:54:34 -0400
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>

On 05 Jun 2016 17:39, Paul Pluzhnikov wrote:
> +static void
> +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);
-mike

Attachment: signature.asc
Description: Digital signature

Follow-Ups:
- Re: Do we care about malloc failure in tests?
  - From: Paul Pluzhnikov
- Re: Do we care about malloc failure in tests?
  - From: Florian Weimer

References:
- Re: Do we care about malloc failure in tests?
  - From: Paul Pluzhnikov

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]