From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by sourceware.org (Postfix) with ESMTPS id 5603F385BAD0 for ; Wed, 29 Jun 2022 15:29:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5603F385BAD0 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 5DA2A1F88F; Wed, 29 Jun 2022 15:29:15 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 44A29132C0; Wed, 29 Jun 2022 15:29:15 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id OPOcD8tvvGKNIQAAMHmgww (envelope-from ); Wed, 29 Jun 2022 15:29:15 +0000 From: Tom de Vries To: gdb-patches@sourceware.org Cc: Tom Tromey Subject: [PATCH 1/5] [COVER-LETTER, RFC] Fix some fsanitize=thread issues in gdb's cooked index Date: Wed, 29 Jun 2022 17:29:10 +0200 Message-Id: <20220629152914.13149-1-tdevries@suse.de> X-Mailer: git-send-email 2.35.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-12.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, KAM_SHORT, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2022 15:29:17 -0000 This is an attempt at fixing some gdb thread sanitizer issues. I used gcc 12 and -fsanitize=thread. The patches address problems in the parallel reading of the cooked index. There are a few problems remaining when testing: - FAILs in test-case gdb.base/early-init-file.exp, submitted test-case patch at https://sourceware.org/pipermail/gdb-patches/2022-June/190343.html - we have a heap-use-after-free in gdb.dwarf2/dw2-icc-opaque.exp. Not thread-related, filed at https://sourceware.org/bugzilla/show_bug.cgi?id=29295. - we run into timeouts in several test-cases: - gdb.gdb/python-helper.exp - gdb.multi/multi-target-thread-find.exp - gdb.threads/break-while-running.exp - gdb.threads/detach-step-over.exp - gdb.threads/fork-thread-pending.exp - gdb.threads/next-fork-other-thread.exp - gdb.threads/pending-fork-event-detach.exp - gdb.threads/wp-replication.exp presumably due to sanitizer overhead. - with tui tests, at the point of calling newterm we run into "WARNING: ThreadSanitizer: unlock of an unlocked mutex (or by a wrong thread)". This is reproducible in a standalone test-case calling newterm, so not related to gdb. Affects: - gdb.python/tui-window.exp - gdb.tui/basic.exp - gdb.tui/empty.exp - gdb.tui/list.exp - gdb.tui/new-layout.exp - gdb.tui/regs.exp - gdb.tui/tui-missing-src.exp - gdb.tui/winheight.exp - gdb.tui/winwidth.exp - We run into 4 reported data races in gdb.base/gdb-sigterm.exp, filed at https://sourceware.org/bugzilla/show_bug.cgi?id=29297. --- gdb/COVER-LETTER | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 gdb/COVER-LETTER diff --git a/gdb/COVER-LETTER b/gdb/COVER-LETTER new file mode 100644 index 00000000000..e69de29bb2d base-commit: 9117c7b452ef76304f4394a97c887d0c4af439f5 -- 2.35.3