From: Mike Frysinger <vapier@gentoo.org>
To: Nick Clifton <nickc@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Commit: Export AArch64 sum's single step function
Date: Thu, 11 Aug 2016 16:20:00 -0000 [thread overview]
Message-ID: <20160811162015.GW30544@vapier.lan> (raw)
In-Reply-To: <e8cad444-bcb7-26a5-6e68-0e3e02d07c43@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
On 11 Aug 2016 16:32, Nick Clifton wrote:
> Hi Mike,
> > this is already possible with the common sim API -- sim_resume() has a
> > "step" argument specifically to do single stepping.
>
> Hmm, OK, but how is this single stepping communicated to the target simulator ?
>
> As far as I can see the AArch64 simulator does not support single stepping
> (unless the host has inserted breakpoint instructions into the simulated instruction
> space). I assume that this is a bug in the aarch64 simulator code, but what exactly
> is wrong ?
>
> Hmm, I see that some other target simulators implement a sim_resume() function of
> their own. Perhaps this is the problem - the aarch64 sim should do the same ?
no, you don't want to implement sim_resume. any sim that does you should
ignore. i think the prob is that the aarch64 sim_engine_run is missing a
call to sim_events_process. look at ft32/interp.c for a bare bones example.
once you do that, you'll see the common sim_resume schedules an event after
one tick when step==true.
honestly, i'm a little surprised things are working w/out this event process
callback ...
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-11 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 14:04 Nick Clifton
2016-08-11 14:21 ` Mike Frysinger
2016-08-11 15:32 ` Nick Clifton
2016-08-11 16:20 ` Mike Frysinger [this message]
2016-08-12 10:40 ` Nick Clifton
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=20160811162015.GW30544@vapier.lan \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.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