From: Andrew Burgess <aburgess@redhat.com>
To: "R. Diez" <rdiezmail-temp2@yahoo.de>, gdb@sourceware.org
Subject: Re: Refresh TUI source panel after "monitor reset"
Date: Fri, 24 Jun 2022 15:05:17 +0100 [thread overview]
Message-ID: <87h74ab1ia.fsf@redhat.com> (raw)
In-Reply-To: <48b5be62-64c1-c7bb-a560-e454ffe2f0ba@yahoo.de>
"R. Diez via Gdb" <gdb@sourceware.org> writes:
> Hi all:
>
> I have been using GDB with OpenOCD for quite a while in order to
> program and debug embedded software on an STM32 microcontroller.
>
> I have learnt that, after a "monitor reset halt" (which resets the
> CPU), GDB still keeps the cached values of the CPU registers, but you
> can workaround it with command "flushregs".
>
> There is one thing that is still bugging me though: in TUI mode, the
> source pane does not refresh until the current instruction is
> executed.
>
> Is there a way to refresh the source pane after "flushregs"? I tried
> "maint flush source-cache" and "refresh", but they did not help.
Completely untested, but I wonder if 'list *$pc' does what you want?
Thanks,
Andrew
next prev parent reply other threads:[~2022-06-24 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48b5be62-64c1-c7bb-a560-e454ffe2f0ba.ref@yahoo.de>
2022-06-21 11:30 ` R. Diez
2022-06-24 14:05 ` Andrew Burgess [this message]
2022-06-24 14:57 ` R. Diez
2022-06-28 13:43 ` Pedro Alves
2022-09-02 12:34 ` R. Diez
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=87h74ab1ia.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb@sourceware.org \
--cc=rdiezmail-temp2@yahoo.de \
/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).