From: John Baldwin <jhb@FreeBSD.org>
To: hilbert <swdtian@163.com>
Cc: gdb@sourceware.org
Subject: Re: Why are these two methods default_memory_insert_breakpoint() and default_memory_remove_breakpoint() called multiple times
Date: Thu, 1 Jun 2023 10:09:40 -0700 [thread overview]
Message-ID: <ea93894a-b761-1041-e926-e3a11e5aa8b4@FreeBSD.org> (raw)
In-Reply-To: <1e72b0a7.2eba.18874a5c3c9.Coremail.swdtian@163.com>
On 5/31/23 6:50 PM, hilbert wrote:
> @John Baldwin
>
>
>
> Thank you very much for your answer;
>
>
>
>
> I have another question, very confused.I don't understand the mechanism of register caching.
>
> The register cache is initialized at the very beginning, when will it be updated later?
>
> Will it be automatically updated later?
My understanding is that the cache for a given thread is flushed on each stop of that thread,
so the cache is only active in terms of preventing multiple ptrace() calls or multiple
requests to the remote target while a user is examining a thread during a single stop.
--
John Baldwin
next prev parent reply other threads:[~2023-06-01 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:12 hilbert via Gdb
2023-05-31 15:57 ` John Baldwin
2023-06-01 1:50 ` hilbert via Gdb
2023-06-01 17:09 ` John Baldwin [this message]
2023-06-02 2:09 ` hilbert via Gdb
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=ea93894a-b761-1041-e926-e3a11e5aa8b4@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=gdb@sourceware.org \
--cc=swdtian@163.com \
/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