public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "luis.machado at arm dot com" <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:32:18 +0000 [thread overview] Message-ID: <bug-21221-4717-qgRKCO5pXh@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 #21 from Luis Machado <luis.machado at arm dot com> --- Thanks for the input. That behavior sounds like a different bug in gdb. When in motion, gdb should always be interruptible so that you don't run into situations like this. There isn't much gdb can do about the tight loops themselves, but there should be a graceful way out of it with the interruption. In the past there used to be a race condition between gdb sending the interrupt request and the remote replying with a stop reply, and then gdb for some reason used to disregard the interrupt request and proceed with the motion (issuing stepi/continue over and over again). I'll have to play with this a bit more to see if I can reproduce the same situation. Unrelated, but I did notice the black magic debugging stub is still using ACK packets though. If it isn't dealing with unreliable communication channels, that can be dropped. -- 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:32 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 2023-02-03 10:32 ` luis.machado at arm dot com [this message] 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-qgRKCO5pXh@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: linkBe 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).