From: Avery Pennarun <apenwarr@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Nicolas Pitre <nico@fluxnic.net>, git@vger.kernel.org
Subject: Re: Completion of error handling
Date: Tue, 2 Feb 2010 14:49:31 -0500 [thread overview]
Message-ID: <32541b131002021149g6ffe703erd9e25621e4305a52@mail.gmail.com> (raw)
In-Reply-To: <4B688042.8090400@web.de>
On Tue, Feb 2, 2010 at 2:42 PM, Markus Elfring <Markus.Elfring@web.de> wrote:
> Nicolas wrote:
>> At least on Linux, most of those functions simply cannot fail.
>
> Would you like to support software environments that work without a
> famous out-of-memory killer?
In many cases on Linux systems, you don't get the OOM notification
anyway until you try to *use* the memory, not at allocation time. So
even checking the results of malloc() won't always save you (although
*not* checking can make problems even worse).
However, for functions that can't allocate memory at all, it's extra
pointless to worry about.
>> There is just no dynamic memory allocation involved.
>
> I find this opinion strange.
This isn't an opinion; because it's open source, you can actually look
at the source code and find out that many system calls don't do memory
allocation at all.
Avery
next prev parent reply other threads:[~2010-02-02 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 13:11 Completion of error handling Markus Elfring
2010-02-02 18:26 ` Nicolas Pitre
2010-02-02 18:49 ` Markus Elfring
2010-02-02 19:27 ` Nicolas Pitre
2010-02-02 19:42 ` Markus Elfring
2010-02-02 19:49 ` Avery Pennarun [this message]
2010-02-02 20:10 ` Markus Elfring
2010-02-02 20:25 ` Avery Pennarun
2010-02-02 21:26 ` Markus Elfring
2010-02-02 21:27 ` Avery Pennarun
2010-02-02 21:55 ` Markus Elfring
2010-02-11 13:08 ` Markus Elfring
2010-02-16 10:56 ` Andreas Ericsson
2010-02-18 15:11 ` Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32541b131002021149g6ffe703erd9e25621e4305a52@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).