This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Do we care about malloc failure in tests?
- From: Paul Pluzhnikov <ppluzhnikov at google 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: Sun, 5 Jun 2016 19:00:30 -0700
- 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 Sun, Jun 5, 2016 at 6:54 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> 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);
Done.
I think I can also remove this from xrealloc, since our realloc does
the right thing when p==NULL.
+ if (p == 0)
+ return xmalloc (n);
Ok to commit with these changes?
Thanks,
--
Paul Pluzhnikov