From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb] Add tsan-suppressions.txt
Date: Tue, 12 Jul 2022 10:39:16 +0200 [thread overview]
Message-ID: <fae76fd5-0785-59d1-81b3-655722a68852@suse.de> (raw)
In-Reply-To: <20220711100825.GA15997@delia.home>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
On 7/11/22 12:08, Tom de Vries wrote:
> Hi,
>
> Add a new file tsan-suppressions.txt, to suppress the "unlock unlocked mutex"
> problem in ncurses, filed in PR29328.
>
> For now, one needs to specify it manually using something like:
> ...
> $ export TSAN_OPTIONS=suppressions=$(pwd -P)/src/gdb/tsan-suppressions.txt
> ...
>
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29328
>
> Any comments?
>
I just found that we already set ASAN_OPTIONS in lib/gdb.exp, so I've
added this TSAN_OPTIONS setting alongside.
Thanks,
- Tom
[-- Attachment #2: 0003-gdb-Add-tsan-suppressions.txt.patch --]
[-- Type: text/x-patch, Size: 2132 bytes --]
[gdb] Add tsan-suppressions.txt
Add a new file tsan-suppressions.txt, to suppress the "unlock unlocked mutex"
problem in ncurses, filed in PR29328.
The file is added to the TSAN_OPTIONS in lib/gdb.exp.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29328
---
gdb/testsuite/lib/gdb.exp | 9 +++++++++
gdb/tsan-suppressions.txt | 18 ++++++++++++++++++
2 files changed, 27 insertions(+)
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index a29b8f947c4..49b00391729 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -32,6 +32,15 @@ if {$tool == ""} {
# (which will affect any spawned sub-process) to avoid this.
append ::env(ASAN_OPTIONS) ",detect_leaks=0"
+set tsan_suppressions suppressions=$srcdir/../tsan-suppressions.txt
+if { ![info exists env(TSAN_OPTIONS) ]
+ || $env(TSAN_OPTIONS) == "" } {
+ set env(TSAN_OPTIONS) "$tsan_suppressions"
+} else {
+ append env(TSAN_OPTIONS) ":$tsan_suppressions"
+}
+unset tsan_suppressions
+
# List of procs to run in gdb_finish.
set gdb_finish_hooks [list]
diff --git a/gdb/tsan-suppressions.txt b/gdb/tsan-suppressions.txt
new file mode 100644
index 00000000000..5f1e5dc7ea7
--- /dev/null
+++ b/gdb/tsan-suppressions.txt
@@ -0,0 +1,18 @@
+# Copyright (C) 2022 Free Software Foundation, Inc.
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+# Problem in ncurses, see:
+# - https://sourceware.org/bugzilla/show_bug.cgi?id=29328.
+# - https://lists.gnu.org/archive/html/bug-ncurses/2022-07/msg00002.html
+mutex:newterm
next prev parent reply other threads:[~2022-07-12 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 10:08 Tom de Vries
2022-07-12 8:39 ` Tom de Vries [this message]
2022-07-12 10:31 ` Tom de Vries
2022-07-12 11:46 ` [committed][gdb] " Tom de Vries
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=fae76fd5-0785-59d1-81b3-655722a68852@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@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).