From: Nick Clifton <nickc@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: Commit: Export AArch64 sum's single step function
Date: Fri, 12 Aug 2016 10:40:00 -0000 [thread overview]
Message-ID: <04eb3f97-8c98-a8a3-14c4-5a489cb7c0f1@redhat.com> (raw)
In-Reply-To: <20160811162015.GW30544@vapier.lan>
Hi Mike,
> 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.
Ah - thanks - that was the pointer I needed. (I kept on looking at the wrong
targets for examples of what to do).
I have now checked in a patch to revert my previous delta - no more exporting
aarch64_step() - and to make aarch64_run process events correctly.
> honestly, i'm a little surprised things are working w/out this event process
> callback ...
It probably wasn't in GDB. I do not use GDB with AArch64 at the moment, so I
had never come across the deficiency. With this patch in it might even work now...
Cheers
Nick
prev parent reply other threads:[~2016-08-12 10:40 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
2016-08-12 10:40 ` Nick Clifton [this message]
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=04eb3f97-8c98-a8a3-14c4-5a489cb7c0f1@redhat.com \
--to=nickc@redhat.com \
--cc=gdb-patches@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