public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sebastien dot decugis at ext dot bull dot net" <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: Fri, 10 Sep 2004 14:52:00 -0000 [thread overview] Message-ID: <20040910145218.9321.qmail@sourceware.org> (raw) In-Reply-To: <20040910141527.379.sebastien.decugis@ext.bull.net> ------- Additional Comments From sebastien dot decugis at ext dot bull dot net 2004-09-10 14:52 ------- Yes I'm using --enable-kernel=2.6.8.1 (with a running kernel 2.6.8.1). Do you tell me to remove the following lines? 368 /* The CLONE_STOPPED flag was introduced in the 2.6.0-test1 series. */ 369 #if __LINUX_KERNEL_VERSION >= 132609 370 # define __ASSUME_CLONE_STOPPED 1 371 #endif Well, if that's it, shouldn't this be considered as a bug ?!? Thanks! Seb. -- 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.
next prev parent reply other threads:[~2004-09-10 14:52 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 [this message] 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
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=20040910145218.9321.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).