Le mardi 08 septembre 2009 à 10:55 +0200, Bernhard R. Link a écrit : > Often there is something sensible: Wait till more memory is available or > just make the operation needing so much memory fail. If it’s an operation that specifically requires much memory, Glib provides g_try_*alloc functions for that. However, when allocations start failing for string manipulation operations, the application is doomed. > 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). When the daemon gets in this situation, it’s very likely to be the first target for the OOM killer. Note that most high-level languages are also going to simply dump an unhandled exception when the process gets out of memory. -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=