* Josselin Mouette <j...@debian.org> [090908 10:45]:
> Le lundi 07 septembre 2009 à 20:00 +0200, Giacomo A. Catenazzi a
> > Steve Langasek wrote:
> > > Case 1, please. Either case 2 fails to handle the allocation error, or
> > > glib
> > > is doing its own abort. Neither is acceptable.
>
> Yeah, sure. As if there was anything more sensible to do than aborting
> when a memory allocation fails. When this happens under Linux, the
> application will end up OOM-killed really soon anyway.
Often there is something sensible: Wait till more memory is available or
just make the operation needing so much memory fail.
It's all a matter of context: for some graphical program it is usually
reasonable to not care and just abort. For some system daemon not
automatically respawned terminating because of some transient condition
is just a bug. (Even if Linux makes it not very easy to catch all
such conditions, not handling accordingly if one detects something like
that has no excuse but laziness).
Hochachtungsvoll,
Bernhard R. Link
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
