public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/386] pthread_create returns ENOMEM but should return EAGAIN
Date: Sun, 26 Sep 2004 12:13:00 -0000	[thread overview]
Message-ID: <20040926121317.10598.qmail@sourceware.org> (raw)
In-Reply-To: <20040915163338.386.sebastien.decugis@ext.bull.net>


------- Additional Comments From drepper at redhat dot com  2004-09-26 12:13 -------
I don't think there is any case left where ENOMEM is returned.  If yes, provide
a test case.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


http://sources.redhat.com/bugzilla/show_bug.cgi?id=386

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2004-09-26 12:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-15 16:33 [Bug nptl/386] New: " sebastien dot decugis at ext dot bull dot net
2004-09-26 12:13 ` drepper at redhat dot com [this message]
2007-03-29 20:11 ` [Bug nptl/386] " 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
     [not found] <bug-386-131@http.sourceware.org/bugzilla/>
2011-05-10  0:28 ` jhaberman at gmail dot com
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

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=20040926121317.10598.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --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).