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 dap/30680] [gdb/dap] ThreadSanitizer: data race gdbsupport/event-pipe.h:44 in event_pipe::is_open() const
Date: Wed, 26 Jul 2023 16:57:37 +0000 [thread overview]
Message-ID: <bug-30680-4717-7RAhAxWcmF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30680-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30680
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 15014
--> https://sourceware.org/bugzilla/attachment.cgi?id=15014&action=edit
LOG.gz
(In reply to Tom de Vries from comment #6)
> and it does trigger.
In a run of 200, 12 times.
There are problems in other test-cases as well:
...
$ grep ERROR:.*sourcing LOG | sort | uniq -c
3 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/ada-scopes.exp.
6 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/args-env.exp.
87 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/basic-dap.exp.
6 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/bt-nodebug.exp.
18 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/catch-exception.exp.
60 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/cond-bp.exp.
24 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/hover.exp.
6 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/log-message.exp.
36 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/modules.exp.
3 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/scopes.exp.
12 ERROR: tcl error sourcing
/data/vries/gdb/src/gdb/testsuite/gdb.dap/stop-at-main.exp.
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-26 16:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 10:33 [Bug dap/30680] New: " vries at gcc dot gnu.org
2023-07-25 10:46 ` [Bug dap/30680] " vries at gcc dot gnu.org
2023-07-25 11:10 ` vries at gcc dot gnu.org
2023-07-25 11:51 ` vries at gcc dot gnu.org
2023-07-25 12:36 ` tromey at sourceware dot org
2023-07-26 12:12 ` vries at gcc dot gnu.org
2023-07-26 16:23 ` vries at gcc dot gnu.org
2023-07-26 16:57 ` vries at gcc dot gnu.org [this message]
2023-07-26 16:59 ` vries at gcc dot gnu.org
2023-07-28 11:01 ` vries at gcc dot gnu.org
2023-07-28 16:04 ` tromey at sourceware dot org
2023-07-28 16:20 ` vries at gcc dot gnu.org
2023-07-28 17:58 ` tromey at sourceware dot org
2023-07-28 18:10 ` tromey at sourceware dot org
2023-07-31 12:37 ` cvs-commit at gcc dot gnu.org
2023-07-31 12:38 ` 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-30680-4717-7RAhAxWcmF@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).