public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jdelvare at suse dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/27581] New: Threaded program crashes under ulimit -s unlimited Date: Mon, 15 Mar 2021 15:46:35 +0000 [thread overview] Message-ID: <bug-27581-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27581 Bug ID: 27581 Summary: Threaded program crashes under ulimit -s unlimited Product: glibc Version: 2.33 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: jdelvare at suse dot de CC: drepper.fsp at gmail dot com Target Milestone: --- Created attachment 13312 --> https://sourceware.org/bugzilla/attachment.cgi?id=13312&action=edit Reproducer I have a simple program using pthreads which runs fine with the default ulimit -s setting (8192) but crashes midway through execution when ran under ulimit -s unlimited: # ulimit -s unlimited # ./thread_stack MAIN 0x7ffe292afc2c THREAD 0x14ae0f69befc START 6 DONE 0x14ae0f5f92a0 START 5 DONE 0x14ae0f556650 START 4 DONE 0x14ae0f4b3a00 Segmentation fault (core dumped) Is this a glibc bug? -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-03-15 15:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-15 15:46 jdelvare at suse dot de [this message] 2021-03-15 15:54 ` [Bug libc/27581] " fweimer at redhat dot com 2021-03-15 19:24 ` hpj at urpla dot net 2021-03-15 21:45 ` carlos at redhat dot com 2021-03-19 10:56 ` jdelvare at suse dot de
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-27581-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).