public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [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
@ 2022-07-07 16:05 vries at gcc dot gnu.org
2022-07-07 18:08 ` [Bug tui/29328] " vries at gcc dot gnu.org
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: vries at gcc dot gnu.org @ 2022-07-07 16:05 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug tui/29328] [gdb/tui] SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread) (/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
2022-07-07 16:05 [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 vries at gcc dot gnu.org
@ 2022-07-07 18:08 ` vries at gcc dot gnu.org
2022-07-11 10:09 ` vries at gcc dot gnu.org
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: vries at gcc dot gnu.org @ 2022-07-07 18:08 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29328
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> 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.
https://lists.gnu.org/archive/html/bug-ncurses/2022-07/msg00002.html
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug tui/29328] [gdb/tui] SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread) (/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
2022-07-07 16:05 [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 vries at gcc dot gnu.org
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
3 siblings, 0 replies; 5+ messages in thread
From: vries at gcc dot gnu.org @ 2022-07-11 10:09 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29328
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch to add suppression in new tsan-suppressions.txt file:
https://sourceware.org/pipermail/gdb-patches/2022-July/190619.html
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug testsuite/29328] [gdb/tui] SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread) (/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
2022-07-07 16:05 [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 vries at gcc dot gnu.org
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 ` vries at gcc dot gnu.org
2022-07-12 11:53 ` vries at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: vries at gcc dot gnu.org @ 2022-07-12 11:52 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29328
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|tui |testsuite
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Not a gdb problem, reclassifying as testsuite problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug testsuite/29328] [gdb/tui] SUMMARY: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread) (/usr/lib64/libtsan.so.2+0x47361) in pthread_mutex_unlock
2022-07-07 16:05 [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 vries at gcc dot gnu.org
` (2 preceding siblings ...)
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
3 siblings, 0 replies; 5+ messages in thread
From: vries at gcc dot gnu.org @ 2022-07-12 11:53 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=29328
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Target Milestone|--- |13.1
Resolution|--- |FIXED
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=09559238fdcca6ffa2ddfdd6a89ac919a9ccb80d
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-07-12 11:53 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-07 16:05 [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 vries at gcc dot gnu.org
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
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).