From: Stefan Weil <weil@mail.berlios.de>
To: Stefano Bonifazi <stefboombastic@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] HELP PLEASE! Consecutive runs of qemu-user
Date: Tue, 04 Jan 2011 11:56:18 +0100 [thread overview]
Message-ID: <4D22FCD2.2080505@mail.berlios.de> (raw)
In-Reply-To: <4D1F9D33.6070805@gmail.com>
Am 01.01.2011 22:31, schrieb Stefano Bonifazi:
> Hi!
> First of all Happy new year to everybody! :) Wish you all to realize
> all your dreams! :)
> I edited QEMU user, more exactly qemu-ppc launching the main function
> (inside main.c) from another c function I created, passing it the
> appropriate parameters.
> I also caught the syscall 1 preventing it to abort the process, and
> simply returning from cpu_loop function, so that this function is not
> more endless, and main returns to my user defined function.
> The problem is that launching a second time main with other parameters
> fails: leaving the code like it was, the previous translated binary
> was kept "in memory" and run again, no matter what binary parameter I
> passed to main.
> I added then tb_flush(env); after cpu_loop inside main..
> But with this edit launching main with other parameters blocks the
> execution at tcg_qemu_tb_exec(tc_ptr); ..It sounds like QEMU stores
> the state of the translation even after main function is over :(
> Is it possible to reset completely the state, allowing consecutive
> runs of different binaries?
> What are the state variables I should "clean" between different runs?
> Thank you very much for your help!
> Best regards!
> Stefano B.
Hi Stefano,
maybe 'qemu -singlestep' helps.
Regards,
Stefan W.
prev parent reply other threads:[~2011-01-04 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 21:31 [Qemu-devel] HELP PLEASE! Consecutive runs of qemu-user Stefano Bonifazi
2011-01-04 10:56 ` Stefan Weil [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=4D22FCD2.2080505@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.org \
--cc=stefboombastic@gmail.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).