public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ourgour at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug linuxthreads/28795] New: Segmentation fault with gcc 4.8.5 during pthread_cleanup_push and pthread_mutex_unlock Date: Thu, 20 Jan 2022 09:35:32 +0000 [thread overview] Message-ID: <bug-28795-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28795 Bug ID: 28795 Summary: Segmentation fault with gcc 4.8.5 during pthread_cleanup_push and pthread_mutex_unlock Product: glibc Version: 2.22 Status: UNCONFIRMED Severity: normal Priority: P2 Component: linuxthreads Assignee: unassigned at sourceware dot org Reporter: ourgour at gmail dot com CC: drow at false dot org Target Milestone: --- Created attachment 13917 --> https://sourceware.org/bugzilla/attachment.cgi?id=13917&action=edit C File to reproduce described issue Hi, I'm working on SUSE Linux 12.4 platform with gcc 4.8.5 and glibc 2.22. I have threading application which fails during pthread_mutex_unlock (which is pushed via pthread_cleanup_push) I've attached source file. Failure can be reproduced when compiled like : gcc -m32 -pthread sapl.c -o sapl.o If it's compiled without -m32 option, it works fine. Also, issue is reproducing for a single thread too. Please help out. Thanks, Digvijay -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-01-20 9:35 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-20 9:35 ourgour at gmail dot com [this message] 2022-01-20 11:24 ` [Bug nptl/28795] " fweimer at redhat dot com 2022-01-21 4:09 ` 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@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).