public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/30261] [gdb] segfaults in gdb.base/index-cache.exp Date: Fri, 31 Mar 2023 14:54:52 +0000 [thread overview] Message-ID: <bug-30261-4717-6YLOL1TaT5@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30261-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30261 --- Comment #10 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6f214d0f399847b13f979651c3b46befcbb42140 commit 6f214d0f399847b13f979651c3b46befcbb42140 Author: Tom Tromey <tom@tromey.com> Date: Fri Mar 24 15:53:22 2023 -0600 Fix race in background index-cache writing Tom de Vries pointed out a bug in the index-cache background writer -- sometimes it will fail. He also noted that it fails when the number of worker threads is set to zero. These turn out to be the same problem -- the cache can't be written to until the per-BFD's "index_table" member is set. This patch avoids the race by rearranging the code slightly, to ensure the cache cannot possibly be written before the member is set. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30261 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-31 14:54 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-22 12:21 [Bug gdb/30261] New: " vries at gcc dot gnu.org 2023-03-22 12:29 ` [Bug gdb/30261] " vries at gcc dot gnu.org 2023-03-22 12:35 ` vries at gcc dot gnu.org 2023-03-22 12:52 ` vries at gcc dot gnu.org 2023-03-22 13:54 ` vries at gcc dot gnu.org 2023-03-23 15:19 ` vries at gcc dot gnu.org 2023-03-23 15:20 ` [Bug symtab/30261] " vries at gcc dot gnu.org 2023-03-23 15:35 ` vries at gcc dot gnu.org 2023-03-23 19:22 ` tromey at sourceware dot org 2023-03-24 20:57 ` tromey at sourceware dot org 2023-03-24 21:55 ` tromey at sourceware dot org 2023-03-31 14:54 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-31 14:55 ` tromey at sourceware dot org
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=bug-30261-4717-6YLOL1TaT5@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).