public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/symtab] Make per_cu->unit_type atomic Date: Thu, 14 Jul 2022 06:19:09 +0000 (GMT) [thread overview] Message-ID: <20220714061909.46F263857C42@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b35bd7d552f80518ad90e81f592b73ee2ef736d7 commit b35bd7d552f80518ad90e81f592b73ee2ef736d7 Author: Tom de Vries <tdevries@suse.de> Date: Thu Jul 14 08:19:00 2022 +0200 [gdb/symtab] Make per_cu->unit_type atomic With gdb with -fsanitize=thread and test-case gdb.ada/array_bounds.exp, I run into a data race between: ... Read of size 1 at 0x7b2000025f0f by main thread: #0 packed<dwarf_unit_type, 1ul>::operator dwarf_unit_type() const packed.h:54 #1 dwarf2_per_cu_data::set_unit_type(dwarf_unit_type) read.h:339 ... and: ... Previous write of size 1 at 0x7b2000025f0f by thread T3: #0 dwarf2_per_cu_data::set_unit_type(dwarf_unit_type) read.h:341 ... Fix this by making per_cu->unit_type atomic. Tested on x86_64-linux. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29286 Diff: --- gdb/dwarf2/read.h | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/gdb/dwarf2/read.h b/gdb/dwarf2/read.h index fcf0cd70530..acbe298b310 100644 --- a/gdb/dwarf2/read.h +++ b/gdb/dwarf2/read.h @@ -178,7 +178,7 @@ public: private: /* The unit type of this CU. */ - packed<dwarf_unit_type, 1> m_unit_type = (dwarf_unit_type) 0; + std::atomic<packed<dwarf_unit_type, 1>> m_unit_type {(dwarf_unit_type)0}; /* The language of this CU. */ packed<language, LANGUAGE_BYTES> m_lang = language_unknown; @@ -329,19 +329,24 @@ public: dwarf_unit_type unit_type (bool strict_p = true) const { + dwarf_unit_type ut = m_unit_type.load (); if (strict_p) - gdb_assert (m_unit_type != 0); - return m_unit_type; + gdb_assert (ut != 0); + return ut; } void set_unit_type (dwarf_unit_type unit_type) { - if (m_unit_type == 0) - /* Set if not set already. */ - m_unit_type = unit_type; - else - /* If already set, verify that it's the same value. */ - gdb_assert (m_unit_type == unit_type); + /* Set if not set already. */ + packed<dwarf_unit_type, 1> nope = (dwarf_unit_type)0; + if (m_unit_type.compare_exchange_strong (nope, unit_type)) + return; + + /* If already set, verify that it's the same value. */ + nope = unit_type; + if (m_unit_type.compare_exchange_strong (nope, unit_type)) + return; + gdb_assert_not_reached (); } enum language lang (bool strict_p = true) const
reply other threads:[~2022-07-14 6:19 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220714061909.46F263857C42@sourceware.org \ --to=vries@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).