From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-mips strange jump !!!
Date: Sat, 27 Dec 2008 16:32:35 +0100 [thread overview]
Message-ID: <fb249edb0812270732w234312bl65327dbe5b44c675@mail.gmail.com> (raw)
In-Reply-To: <fb249edb0812270324w7eeb9035uc75cd5a209680762@mail.gmail.com>
2008/12/27 andrzej zaborowski <balrogg@gmail.com>:
> 2008/12/27 Laurent Desnogues <laurent.desnogues@gmail.com>:
>> On Fri, Dec 26, 2008 at 7:36 PM, Alessandro Montano <alex@exit.it> wrote:
>>> This is my first post, so sorry for any error ...
>>> I'm developing a DVB-S emulator based on qemu-mips.
>>> I'm adding all the device, once a time, but I notice a strange problem that
>>> crashes my emulator.
>>>
>>> It seems to do bad jumps!
>>>
>>> In brief ... I run this command
>>> *./bin/-qemu-system-mips -L . mips_bios.bin -d int,exec,op,in_asm
>>> *and it genereates this log
>>>
>>> IN:
>>> 0x80071fc4: lui at,0x8007
>>> 0x80071fc8: lw a1,0xC094(at)
>>> 0x80071fcc: lui a0,0x8007
>>> 0x80071fd0: addiu a0,a0,0xD060
>>> 0x80071fd4: jal 0x8006d76c <- this is the right address
>>> 0x80071fd8: nop
>> [...]
>>> IN:
>>> 0x8006d968: andi t9,t9,0xdf <- but this is a wrong jump !!!
>>> 0x8006d96c: j 0x8006d90c
>>> 0x8006d970: ori t9,t9,0x20
>>
>> You can't rely on logs to see the flow of a program.
>
> Not with "in_asm" alone, but "exec" should show the flow of execution,
> except DEBUG_EXEC is undefined by default.
Actually no, Laurent pointed out that even this will not show what I
would expect when TBs are chained.
Cheers
prev parent reply other threads:[~2008-12-27 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812240123.mBO1N2NJ029937@fedora.exit.it>
2008-12-26 18:36 ` [Qemu-devel] qemu-mips strange jump !!! Alessandro Montano
2008-12-27 8:24 ` Laurent Desnogues
2008-12-27 11:24 ` andrzej zaborowski
2008-12-27 15:32 ` andrzej zaborowski [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=fb249edb0812270732w234312bl65327dbe5b44c675@mail.gmail.com \
--to=balrogg@gmail.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).