From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Sandra Loosemore <sandra@codesourcery.com>,
qemu-devel@nongnu.org, marex@denx.de, crwulff@gmail.com
Subject: Re: [Qemu-devel] [PATCH] Fix breakpoints in nios2 user-mode emulation.
Date: Wed, 12 Sep 2018 19:39:41 +0100 [thread overview]
Message-ID: <87ftyeblw2.fsf@linaro.org> (raw)
In-Reply-To: <618b095d-d3fd-4cbb-f2ba-37e0f4902f28@linaro.org>
Richard Henderson <richard.henderson@linaro.org> writes:
> On 09/11/2018 02:29 PM, Sandra Loosemore wrote:
>> Without this patch, QEMU exits immediately when it execution stops at
>> a breakpoint, instead of reporting it to GDB.
>>
>> Signed-off-by: Sandra Loosemore <sandra@codesourcery.com>
>> ---
>> linux-user/nios2/cpu_loop.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/linux-user/nios2/cpu_loop.c b/linux-user/nios2/cpu_loop.c
>> index dac7a06..a5ae37f 100644
>> --- a/linux-user/nios2/cpu_loop.c
>> +++ b/linux-user/nios2/cpu_loop.c
>> @@ -71,6 +71,9 @@ void cpu_loop(CPUNios2State *env)
>> gdbsig = TARGET_SIGTRAP;
>> break;
>> }
>> + case EXCP_DEBUG:
>> + gdbsig = TARGET_SIGTRAP;
>> + break;
>
> This really isn't complete. You set gdbsig from odd places instead of using
> queue_signal; you fail to honor the return value from gdb_handlesig.
>
> But I suppose those should be separate patches, so
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
At least the cpu_loops have been separated now.. I guess the next step
is to audit each one for common features? There do seem to be some magic
numbers in the nios loop which I find concerning.
>
>
> r~
--
Alex Bennée
next prev parent reply other threads:[~2018-09-12 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 21:29 [Qemu-devel] [PATCH] Fix breakpoints in nios2 user-mode emulation Sandra Loosemore
2018-09-12 17:49 ` Richard Henderson
2018-09-12 18:01 ` Sandra Loosemore
2018-09-12 18:39 ` Alex Bennée [this message]
2018-09-12 19:31 ` Sandra Loosemore
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=87ftyeblw2.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=crwulff@gmail.com \
--cc=marex@denx.de \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sandra@codesourcery.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;
as well as URLs for NNTP newsgroup(s).