public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30630] remote.c:8352: internal-error: wait: Assertion `!async_event_handler_marked (rs->remote_async_inferior_event_token)' failed.
Date: Tue, 03 Oct 2023 13:48:44 +0000 [thread overview]
Message-ID: <bug-30630-4717-6mBPzTaqWE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30630-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30630
Simon Marchi <simon.marchi at polymtl dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simon.marchi at polymtl dot ca
--- Comment #9 from Simon Marchi <simon.marchi at polymtl dot ca> ---
Thanks for digging into the problem. Can you please send your patch to the
gdb-patches mailing list? Reviews happen there.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-03 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 9:16 [Bug gdb/30630] New: " christian.prochaska@genode-labs.com
2023-08-23 4:28 ` [Bug gdb/30630] " rajesh.palla at amd dot com
2023-08-23 18:13 ` tromey at sourceware dot org
2023-08-31 23:34 ` Mikhail.Terekhov at dell dot com
2023-09-01 0:02 ` Mikhail.Terekhov at dell dot com
2023-09-01 0:23 ` Mikhail.Terekhov at dell dot com
2023-09-01 1:00 ` christian.prochaska@genode-labs.com
2023-09-01 15:15 ` Mikhail.Terekhov at dell dot com
2023-09-05 22:59 ` Mikhail.Terekhov at dell dot com
2023-10-02 22:12 ` Mikhail.Terekhov at dell dot com
2023-10-03 13:48 ` simon.marchi at polymtl dot ca [this message]
2023-10-10 16:42 ` cvs-commit 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-30630-4717-6mBPzTaqWE@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).