public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "rajesh.palla at amd dot com" <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: Wed, 23 Aug 2023 04:28:13 +0000	[thread overview]
Message-ID: <bug-30630-4717-lz81hxOPn3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30630-4717@http.sourceware.org/bugzilla/>

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

Palla, Rajesh <rajesh.palla at amd dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rajesh.palla at amd dot com

--- Comment #1 from Palla, Rajesh <rajesh.palla at amd dot com> ---
I too have similar issue with gdb12.x version. Attaching the gdb remote stub
log

GDB -> $QNonStop:1#8d
GDB <- $OK#9a
GDB -> $qfThreadInfo#bb
GDB <- $mp1.1,p1.2#9a
GDB -> $qsThreadInfo#c8
GDB <- $l#6c
GDB -> $qAttached:1#fa
GDB <- $1#31
GDB -> $qXfer:exec-file:read:1:0,1000#4a
GDB <- $E01#a6
GDB -> $qXfer:exec-file:read:1:0,1000#4a
GDB <- $E01#a6
GDB -> $qTStatus#49
GDB <- $T0#84
GDB -> $qTfV#81
GDB <- $#00
GDB -> $?#3f
GDB <- $T05thread:p1.1;#a6
GDB -> $vStopped#55
GDB <- $T05thread:p1.2;#a7
GDB -> $vStopped#55
GDB <- $OK#9a

remote.c:8334: internal-error: wait: Assertion `!async_event_handler_marked
(rs->remote_async_inferior_event_token)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

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

  reply	other threads:[~2023-08-23  4:28 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 ` rajesh.palla at amd dot com [this message]
2023-08-23 18:13 ` [Bug gdb/30630] " 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
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-lz81hxOPn3@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).