public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "knielson at adaptivecomputing dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/16299] New: pthread_attr_setstacksize ignored Date: Fri, 06 Dec 2013 20:33:00 -0000 [thread overview] Message-ID: <bug-16299-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16299 Bug ID: 16299 Summary: pthread_attr_setstacksize ignored Product: glibc Version: 2.18 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: knielson at adaptivecomputing dot com CC: drepper.fsp at gmail dot com The stack size value set with pthread_attr_setstacksize is ignored when a thread is started using pthread_create. For example, if ulimit -s is set to 8192 and then you try to set the stack size to 4096 the call to pthread_attr_setstacksize succeeds. pthread_attr_getstacksize will return 4096 as well. But when the thread is created it uses the 8192 value as the basis for the stack. It does not make a difference if you try to increase or decrease the stack size of the thread. The default value is always used. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-12-06 20:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-06 20:33 knielson at adaptivecomputing dot com [this message] 2013-12-06 20:53 ` [Bug libc/16299] " bugdal at aerifal dot cx 2013-12-06 21:10 ` knielson at adaptivecomputing dot com 2013-12-06 21:15 ` bugdal at aerifal dot cx 2013-12-06 21:18 ` knielson at adaptivecomputing dot com 2013-12-06 21:32 ` knielson at adaptivecomputing dot com 2013-12-06 22:31 ` carlos at redhat dot com 2013-12-06 22:44 ` knielson at adaptivecomputing dot com 2013-12-06 22:45 ` carlos at redhat dot com 2014-06-13 11:28 ` fweimer 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-16299-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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).