From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D56173852743; Tue, 28 Jun 2022 05:48:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D56173852743 From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/29286] SUMMARY: ThreadSanitizer: data race gdb/dwarf2/read.c:4100 in dw_expand_symtabs_matching_file_matcher Date: Tue, 28 Jun 2022 05:48:57 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2022 05:48:57 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29286 --- Comment #16 from Tom de Vries --- (In reply to Tom de Vries from comment #15) > Created attachment 14180 [details] > Patch fixing all detected data races [gdb/symtab] Fix some data races Fix some data races reported by thread sanitizer. When build with -fsanitize=3Dthread and gcc 12, passes testsuite with no data races. There are a few problems when testing: - we have a heap-use-after-free in gdb.dwarf2/dw2-icc-opaque.exp, but that's a known issue, also triggers with -fsanitize-address. Reported at PR25723 comment 1. - we run into timeouts in test-cases gdb.gdb/python-helper.exp and gdb.threads/detach-step-over.exp, presumably due to sanitizer overhead. - with all tui test, at the point of calling newterm we run into "WARNING: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)". This also happens when first setting "maint set worker-threads 0", so this doesn't seem to be related to gdb's multi-threading behaviour. --=20 You are receiving this mail because: You are on the CC list for the bug.=