public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29359] New: [gdb/build] Flush out thread sanitizer issues
Date: Tue, 12 Jul 2022 15:20:19 +0000	[thread overview]
Message-ID: <bug-29359-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29359

            Bug ID: 29359
           Summary: [gdb/build] Flush out thread sanitizer issues
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

In PR29286 I ran into a few race condition that are now hard to reproduce, but
not fixed AFAICT.

See f.i. the patch at PR 29286 comment 6.

Which made me wonder which other race conditions are lurking.

I wonder if there's anything I can do to flush these out.

>From what I understand, the race conditions are due to executing this:
...
void
cooked_index::finalize ()
{
  m_future = gdb::thread_pool::g_thread_pool->post_task ([this] ()
    {
      do_finalize ();
    });
}
...
and not waiting for it, so perhaps adding a sleep () here could help?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-07-12 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 15:20 vries at gcc dot gnu.org [this message]
2022-07-13  5:57 ` [Bug build/29359] " vries at gcc dot gnu.org
2022-07-13  6:06 ` vries at gcc dot gnu.org
2022-07-13 17:00 ` tromey at sourceware dot org
2022-07-18 10:13 ` vries at gcc dot gnu.org
2022-11-10  7:14 ` vries at gcc dot gnu.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-29359-4717@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: 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).