public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jhaberman at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/386] pthread_create returns ENOMEM but should return EAGAIN
Date: Tue, 10 May 2011 00:28:00 -0000 [thread overview]
Message-ID: <bug-386-131-y1K2eWin9K@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-386-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=386
Josh Haberman <jhaberman at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |jhaberman at gmail dot com
Resolution|WORKSFORME |
--- Comment #9 from Josh Haberman <jhaberman at gmail dot com> 2011-05-10 00:27:37 UTC ---
I was just able to reproduce this. Using strace I discovered that ENOMEM was
coming from the mprotect() call that sets up the guard page. And indeed this
seems to be a case that isn't converting ENOMEM -> EAGAIN.
http://sourceware.org/git/?p=glibc.git;a=blob;f=nptl/allocatestack.c;h=ba251b91626cd1463a19f9db3fbed85eec585897;hb=be9c5e8b2014bdbf724f206bb25249c67115db49#l636
mprotect() returns ENOMEM if you've hit the maximum number of mappings for a
process (which on Linux is currently is 65050).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next parent reply other threads:[~2011-05-10 0:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-386-131@http.sourceware.org/bugzilla/>
2011-05-10 0:28 ` jhaberman at gmail dot com [this message]
2011-05-11 22:24 ` drepper.fsp at gmail dot com
2014-02-16 19:39 ` jackie.rosen at hushmail dot com
2014-05-28 19:44 ` schwab at sourceware dot org
2004-09-15 16:33 [Bug nptl/386] New: " sebastien dot decugis at ext dot bull dot net
2004-09-26 12:13 ` [Bug nptl/386] " drepper at redhat dot com
2007-03-29 20:11 ` mmontgomery at mysql dot com
2007-06-13 20:37 ` anton_ghiugan at ml dot com
2007-10-07 22:13 ` drepper at redhat dot com
2008-07-03 13:52 ` halesh dot s at gmail dot com
2008-07-03 13:54 ` halesh dot s at gmail dot com
2008-07-03 13:54 ` halesh dot s at gmail dot com
2008-07-26 23:52 ` drepper at redhat dot com
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=bug-386-131-y1K2eWin9K@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).