public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "darius at dons dot net.au" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/21221] gdb hangs while stepping an empty loop
Date: Fri, 03 Feb 2023 10:23:24 +0000 [thread overview]
Message-ID: <bug-21221-4717-kSxHBe6zTr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21221-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21221
--- Comment #20 from Daniel O'Connor <darius at dons dot net.au> ---
(In reply to Luis Machado from comment #19)
> When it happens, can you actually interrupt it so you regain control of gdb?
No, it's stuck sending this to the remote debugger:
Breakpoint 1, i2c_write7_v1 (i2c=1073763328, addr=80, data=0x2001ffa4 "", n=2,
start=true) at hal.c:62
62 if (start) {
(gdb) next
63 for (tout = I2C_TIMEOUT; tout > 0 && (I2C_SR2(i2c) &
I2C_SR2_BUSY); tout--)
(gdb) set debug remote 1
(gdb) next
[remote] Sending packet: $Z1,8000546,2#7c
[remote] Received Ack
[remote] Packet received: OK
[remote] Sending packet: $m800054e,2#61
[remote] Received Ack
[remote] Packet received: 404b
[remote] Sending packet: $m800054e,2#61
[remote] Received Ack
[remote] Packet received: 404b
[remote] Sending packet: $m8000550,2#2d
[remote] Received Ack
[remote] Packet received: 7b61
[remote] Sending packet: $m800054e,4#63
[remote] Received Ack
[remote] Packet received: 404b7b61
[remote] Sending packet: $m800054e,2#61
[remote] Received Ack
[remote] Packet received: 404b
[remote] Sending packet: $m800054e,2#61
[remote] Received Ack
[remote] Packet received: 404b
[remote] Sending packet: $Z1,8000550,2#77
[remote] Received Ack
[remote] Packet received: OK
[remote] Sending packet: $c#63
[remote] Received Ack
[remote] wait: enter
[remote] wait: exit
[remote] wait: enter
[remote] Packet received: T05
[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 1
[remote] select_thread_for_ambiguous_stop_reply: is this guess ambiguous? =
0
[remote] select_thread_for_ambiguous_stop_reply: exit
[remote] wait: exit
(See
https://github.com/blackmagic-debug/blackmagic/issues/190#issuecomment-1327190470)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-03 10:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21221-4717@http.sourceware.org/bugzilla/>
2020-04-30 20:41 ` luis.machado at linaro dot org
2020-05-19 4:53 ` luis.machado at linaro dot org
2022-11-25 12:55 ` darius at dons dot net.au
2022-11-25 13:02 ` luis.machado at arm dot com
2022-11-27 2:51 ` darius at dons dot net.au
2023-01-31 10:18 ` kristof.mulier at telenet dot be
2023-01-31 10:39 ` luis.machado at arm dot com
2023-01-31 10:51 ` kristof.mulier at telenet dot be
2023-01-31 11:40 ` luis.machado at arm dot com
2023-01-31 15:00 ` kristof.mulier at telenet dot be
2023-02-03 10:20 ` luis.machado at arm dot com
2023-02-03 10:23 ` darius at dons dot net.au [this message]
2023-02-03 10:32 ` luis.machado at arm dot com
2023-02-06 17:53 ` pedro at palves dot net
2023-03-09 12:49 ` ahmet_kcbyk at hotmail dot com
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-21221-4717-kSxHBe6zTr@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).