From: William Tambe <tambewilliam@gmail.com>
To: gdb@sourceware.org
Subject: Re: Function used by GDB to access target sim memory
Date: Sun, 18 Aug 2019 18:04:00 -0000 [thread overview]
Message-ID: <CAF8i9mM7u9ikdwc1xcKWy9f27+inMTK0t2Zc9DPagcXsVKFCcA@mail.gmail.com> (raw)
In-Reply-To: <CAF8i9mP9Bvz_e4hUJ+uTHkMo8SgLchWPMRMf2-dz+hTHuWNj2A@mail.gmail.com>
To expand on my previous email, I am looking to implement an address
translation layer between GDB and the simulator memory.
Is there a way to set a function that gets called when a request to
access the simulator memory occur ?
On Sun, Aug 18, 2019 at 12:55 PM William Tambe <tambewilliam@gmail.com> wrote:
>
> What function does GDB use to access the simulator memory when "target
> sim" is in use ?
>
> For instance, to implement the access to the simulator registers, one must use:
> CPU_REG_FETCH()
> CPU_REG_STORE()
>
> Are there similar functions for accessing the simulator memory ?
next prev parent reply other threads:[~2019-08-18 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 17:55 William Tambe
2019-08-18 18:04 ` William Tambe [this message]
2019-08-19 19:18 ` Pedro Alves
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=CAF8i9mM7u9ikdwc1xcKWy9f27+inMTK0t2Zc9DPagcXsVKFCcA@mail.gmail.com \
--to=tambewilliam@gmail.com \
--cc=gdb@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