From: Marius Groeger <mgroeger@sysgo.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Single stepping for PPC broken?
Date: Wed, 9 Jan 2008 08:59:35 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0801090849090.6836@localhost> (raw)
Hello all,
I'm having problems with qemu's (-M prep, -cpu 604) handling of the
MSR_SE bit. My gdbstub can successfully step along regular code, but
qemu chokes when stepping over a branch instruction like "blr".
(Needless to say, that same gdbstub works fine on real hardware). I
tried older versions of qemu and found that the code base 8 months ago
worked fine.
I'd like to try this with Linux and gdbserver (or a native gdb) but I
don't have any boot images handy and oszoo.org seems to be down right
now.
Any ideas? Did perhaps the PPC440 additions add some regression here?
Can someone try booting Linux on qemu-system-ppc and try
gdb/gdbserver?
(I haven't been following this list lately, so please bear with me if
I missed something critical. I've searched the archives, of course,
but to no avail.)
Regards and TIA,
Marius
--
Marius Groeger <mgroeger@sysgo.com>
SYSGO AG Embedded and Real-Time Software
Voice: +49 6136 9948 0 FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.pikeos.com
next reply other threads:[~2008-01-09 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 7:59 Marius Groeger [this message]
2008-01-09 12:19 ` [Qemu-devel] Single stepping for PPC broken! Marius Groeger
2008-01-10 13:57 ` [PATCH][Qemu-devel] " Marius Groeger
2008-02-11 23:22 ` Rob Landley
2008-02-13 8:46 ` Marius Groeger
2008-02-13 13:44 ` Daniel Jacobowitz
2008-02-13 15:52 ` Marius Groeger
2008-02-13 16:19 ` Daniel Jacobowitz
2008-02-14 7:36 ` Marius Groeger
2008-03-11 23:16 ` Jason Wessel
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=Pine.LNX.4.64.0801090849090.6836@localhost \
--to=mgroeger@sysgo.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).