public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/29328] New: [gdb/tui] SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread) (/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
Date: Thu, 07 Jul 2022 16:05:47 +0000 [thread overview]
Message-ID: <bug-29328-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29328
Bug ID: 29328
Summary: [gdb/tui] SUMMARY: ThreadSanitizer: unlock of an
unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in
pthread_mutex_unlock
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
When building gdb using thread sanitizer and running the gdb test-suite, I run
into a fair amount of these:
...
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)
(/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
...
AFAICT, this is a problem in ncurses. I've sent an email to
bug-ncurses@gnu.org , I'll post a link once it's published in the archives.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-07-07 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 16:05 vries at gcc dot gnu.org [this message]
2022-07-07 18:08 ` [Bug tui/29328] " vries at gcc dot gnu.org
2022-07-11 10:09 ` vries at gcc dot gnu.org
2022-07-12 11:52 ` [Bug testsuite/29328] " vries at gcc dot gnu.org
2022-07-12 11:53 ` vries at gcc dot gnu.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=bug-29328-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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: link
Be 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).