public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/28795] Segmentation fault with gcc 4.8.5 during pthread_cleanup_push and pthread_mutex_unlock Date: Thu, 20 Jan 2022 11:24:12 +0000 [thread overview] Message-ID: <bug-28795-131-SZ0AJtEYU7@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28795-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28795 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-01-20 Status|UNCONFIRMED |WAITING Flags| |security- CC| |drepper.fsp at gmail dot com, | |fweimer at redhat dot com Ever confirmed|0 |1 Component|linuxthreads |nptl --- Comment #1 from Florian Weimer <fweimer at redhat dot com> --- I can't reproduce this with more recent distribution builds. There were some issues with the old x86 assembler implementations of locking primitives, and we have since removed them. I suggest to reach out to SUSE to see if they can apply relevant fixes to their distribution. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-20 11:24 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-20 9:35 [Bug linuxthreads/28795] New: " ourgour at gmail dot com 2022-01-20 11:24 ` fweimer at redhat dot com [this message] 2022-01-21 4:09 ` [Bug nptl/28795] " ourgour at gmail dot com 2022-01-21 8:37 ` 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-28795-131-SZ0AJtEYU7@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).