public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "abidh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/30054] New: qC response is ignored with S packet.
Date: Thu, 26 Jan 2023 10:09:51 +0000 [thread overview]
Message-ID: <bug-30054-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30054
Bug ID: 30054
Summary: qC response is ignored with S packet.
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: remote
Assignee: unassigned at sourceware dot org
Reporter: abidh at sourceware dot org
Target Milestone: ---
We have noticed a change in behaviour since
24ed6739b699f329c2c45aedee5f8c7d2f54e493. Please see the log below. Targets
send a S00 packet in the start. GDB gets the thread information using qC packet
and target supplies that information in the response. Later GDB ignores it and
picks the first thread anyway.
I investigated it a bit and it seems that thread information that was obtained
in start_remote_1 gets overwritten by switch_to_inferior_no_thread. Later when
S00 packet is processed, it obviously does not have thread information and GDB
ends up calling select_thread_for_ambiguous_stop_reply.
[remote] Sending packet: $qTStatus#49
[remote] Packet received:
[remote] packet_ok: Packet qTStatus (trace-status) is NOT supported
[remote] Sending packet: $?#3f
[remote] Packet received: S00
[remote] Sending packet: $qfThreadInfo#bb
[remote] Packet received: mp2890.1
[remote] Sending packet: $qsThreadInfo#c8
[remote] Packet received: mp2890.2
[remote] Sending packet: $qsThreadInfo#c8
[remote] Packet received: mp2890.3
[remote] Sending packet: $qsThreadInfo#c8
[remote] Packet received: mp2890.4
[remote] Sending packet: $qsThreadInfo#c8
[remote] Packet received: l
[remote] Sending packet: $qAttached:2890#9c
[remote] Packet received:
[remote] packet_ok: Packet qAttached (query-attached) is NOT supported
[remote] Sending packet: $Hc-1#09
[remote] Packet received: OK
[remote] Sending packet: $qC#b4
[remote] Packet received: QCp2890.3
[remote] Sending packet: $qOffsets#4b
[remote] Packet received:
[remote] wait: enter
[remote] select_thread_for_ambiguous_stop_reply: enter
[remote] select_thread_for_ambiguous_stop_reply: process_wide_stop = 0
[remote] select_thread_for_ambiguous_stop_reply: first resumed thread is
Thread 10384.1
[remote] select_thread_for_ambiguous_stop_reply: is this guess ambiguous?
= 1
warning: multi-threaded target stopped without sending a thread-id, using first
non-exited thread
[remote] select_thread_for_ambiguous_stop_reply: exit
[remote] wait: exit
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-01-26 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 10:09 abidh at sourceware dot org [this message]
2023-01-26 10:12 ` [Bug remote/30054] " abidh 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-30054-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).