From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
"Christopher S. Aker" <caker@theshore.net>
Subject: Re: [uml-devel] init_new_context_skas - new_mm failed, errno = -24
Date: Tue, 11 Sep 2007 10:58:52 -0400 [thread overview]
Message-ID: <20070911145852.GB7551@c2.user-mode-linux.org> (raw)
In-Reply-To: <200709111601.03376.blaisorblade@yahoo.it>
On Tue, Sep 11, 2007 at 04:00:58PM +0200, Blaisorblade wrote:
> errno = 24 means EMFILE (too many open files).
Whoops, I mentally turned that into -ENOMEM.
Maybe we should resurrect os_print_error as you suggested and start
using it. The current habit of using raw errnos dates from very
early, when perror (or strerror - I don't remember which) gave me
undebuggable segfaults deep inside libc. Probably, that's not a
problem any more.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2007-09-11 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 15:03 [uml-devel] init_new_context_skas - new_mm failed, errno = -24 Christopher S. Aker
2007-09-10 16:14 ` Jeff Dike
2007-09-10 23:06 ` Christopher S. Aker
2007-09-11 14:00 ` Blaisorblade
2007-09-11 14:58 ` Jeff Dike [this message]
2007-09-11 15:14 ` Blaisorblade
2007-09-21 18:41 ` Jeff Dike
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=20070911145852.GB7551@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=caker@theshore.net \
--cc=user-mode-linux-devel@lists.sourceforge.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