Date: Mon, 17 Dec 2007 12:30:55 -0500 From: David Schultz <das@FreeBSD.ORG> To: Dan Lukes <dan@obluda.cz> Cc: freebsd-bugs@FreeBSD.ORG, Bruce Evans <brde@optusnet.com.au> Subject: Re: bin/83347: [patch] improper handling of malloc failures within libc's vfprintf Message-ID: <20071217173055.GC11621@VARK.MIT.EDU> In-Reply-To: <4766AE99.6040405@obluda.cz> References: <200712170718.lBH7Iuoa026349@freefall.freebsd.org> <20071218033221.X31158@delplex.bde.org> <4766AE99.6040405@obluda.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 17, 2007, Dan Lukes wrote: > Bruce Evans napsal/wrote, On 12/17/07 17:49: > >I prefer following the NULL pointer to aborting. > > Are you sure the *(NULL) raise exception on all platforms (at least > on supported platforms) ? Quite sure. > The professional applications shall never failed by the uncontrolled > way saying just "internal error" to user. It can be acceptable for > gurus, but it's not so nice for casual users. It could be refactored to return ENOMEM, which is arguably better. But crashing in a complicated way isn't any better than crashing in a simple way.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071217173055.GC11621>