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, 25 Nov 2022 12:55:06 +0000 [thread overview]
Message-ID: <bug-21221-4717-aWDJYvUxNW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21221-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21221
Daniel O'Connor <darius at dons dot net.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |darius at dons dot net.au
--- Comment #11 from Daniel O'Connor <darius at dons dot net.au> ---
I just ran into this issue recently using a Black Magic probe to debug an STM32
and I think it is also a GDB bug.
When this is triggered you have to kill GDB because ctrl-c does not interrupt
it.
See this bug report: https://github.com/blackmagic-debug/blackmagic/issues/190
Notably GDB is not hung, nor is the BMP probe - GDB is simply stuck in a loop
talking to the BMP setting breakpoints etc.
I don't really know where to start looking in the GDB code to see why it blocks
being interrupted though so it's hard to see how difficult it would be to
mitigate the problem.
Obviously with the 'nop' work around it's not a big deal but it was quite a
frustrating experience until I learnt that :)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-25 12:55 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 [this message]
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
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-aWDJYvUxNW@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).