From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [patch] gdb-stub support for Alpha
Date: Thu, 04 Dec 2008 16:58:23 +0100 [thread overview]
Message-ID: <4937FE1F.4000803@siemens.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0812040023590.2608-100000@cacao.csl.cornell.edu>
Vince Weaver wrote:
> Here's an updated version of the patch. It fixes floating point support.
>
> It still double-steps after a branch for some reason though.
I would suggest checking out what gets translated, executed and
communicated by using '-d in_asm,out_asm' for the qemu command line,
running qemu itself inside gdb and maybe also enabling 'set debug remote
1' in the remote gdb instance (which will print the frontend<->backend
communication). That should help to get a better picture about what
happens and why you see double steps.
Jan
--
Siemens AG, Corporate Technology, CT SE 26
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2008-12-04 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 18:16 [Qemu-devel] [patch] gdb-stub support for Alpha Vince Weaver
2008-12-04 5:25 ` Vince Weaver
2008-12-04 15:58 ` Jan Kiszka [this message]
2008-12-04 19:26 ` [Qemu-devel] " Vince Weaver
2008-12-07 23:26 ` [Qemu-devel] " Aurelien Jarno
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=4937FE1F.4000803@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).