public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/379] pthread_create fails but the thread executes some instructions Date: Thu, 16 Sep 2004 23:23:00 -0000 [thread overview] Message-ID: <20040916232332.11777.qmail@sourceware.org> (raw) In-Reply-To: <20040910141527.379.sebastien.decugis@ext.bull.net> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-09-16 23:23 ------- Subject: Bug 379 CVSROOT: /cvs/glibc Module name: libc Changes by: roland@sources.redhat.com 2004-09-16 23:23:21 Modified files: nptl : pthread_create.c allocatestack.c Log message: 2004-09-10 Roland McGrath <roland@redhat.com> [BZ #379] * allocatestack.c (allocate_stack): Remove [__ASSUME_CLONE_STOPPED] code, since we don't try to use the broken CLONE_STOPPED any more. * pthread_create.c (start_thread): Likewise. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/nptl/pthread_create.c.diff?cvsroot=glibc&r1=1.33&r2=1.34 http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/nptl/allocatestack.c.diff?cvsroot=glibc&r1=1.48&r2=1.49 -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=379 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
prev parent reply other threads:[~2004-09-16 23:23 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-10 14:15 [Bug nptl/379] New: " sebastien dot decugis at ext dot bull dot net 2004-09-10 14:17 ` [Bug nptl/379] " sebastien dot decugis at ext dot bull dot net 2004-09-10 14:36 ` jakub at redhat dot com 2004-09-10 14:52 ` sebastien dot decugis at ext dot bull dot net 2004-09-10 15:10 ` sebastien dot decugis at ext dot bull dot net 2004-09-12 5:58 ` drepper at redhat dot com 2004-09-16 23:23 ` cvs-commit at gcc dot gnu dot org [this message]
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=20040916232332.11777.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: linkBe 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).