[Qemu-devel] Where are i386 flags??
Where I can find i386 flags after every instruction??
[Qemu-devel] I386 Flags after run TB
I run qemu in single step mode and user-mode. I want to know where i386 flags are stored after a run of one Translation Block.
[Qemu-devel] I386 Flags after run TB
I run qemu in single step mode and user-mode. I want to know where i386 flags are stored after a run of one Translation Block.
[Qemu-devel] Compiling static
I want compile qemu with --static: ./configure --static --target-list=i386-linux-user,arm-linux-user --python=/usr/bin/python2.7 --prefix=/install_qemu Qemu returns: /usr/bin/ld: cannot find -lssl3 /usr/bin/ld: cannot find -lsmime3 /usr/bin/ld: cannot find -lnss3 /usr/bin/ld: cannot find -lnssutil3 collect2: error: ld returned 1 exit status Where can I find these librarys???
[Qemu-devel] Compiling static
Those is my post. This problem is only my. I don't find these library. I don't know where to download them. On 06/28/12 10:22, Dunrong Huang wrote: This post may give you some advice http://lists.gnu.org/archive/html/qemu-devel/2012-06/msg02319.html 2012/6/28 Davide Ferraretto femudevelopm...@gmail.com: I want compile qemu with --static: ./configure --static --target-list=i386-linux-user,arm-linux-user --python=/usr/bin/python2.7 --prefix=/install_qemu Qemu returns: /usr/bin/ld: cannot find -lssl3 /usr/bin/ld: cannot find -lsmime3 /usr/bin/ld: cannot find -lnss3 /usr/bin/ld: cannot find -lnssutil3 collect2: error: ld returned 1 exit status Where can I find these librarys???
[Qemu-devel] Compiling static
I want compile qemu with --static: ./configure --static --target-list=i386-linux-user,arm-linux-user --python=/usr/bin/python2.7 --prefix=/install_qemu Qemu returns: /usr/bin/ld: cannot find -lssl3 /usr/bin/ld: cannot find -lsmime3 /usr/bin/ld: cannot find -lnss3 /usr/bin/ld: cannot find -lnssutil3 collect2: error: ld returned 1 exit status How resolve??
[Qemu-devel] Compiling static
I want compile qemu with --static: ./configure --static --target-list=i386-linux-user,arm-linux-user --python=/usr/bin/python2.7 --prefix=/install_qemu Qemu returns: /usr/bin/ld: cannot find -lssl3 /usr/bin/ld: cannot find -lsmime3 /usr/bin/ld: cannot find -lnss3 /usr/bin/ld: cannot find -lnssutil3 collect2: error: ld returned 1 exit status How resolve??
[Qemu-devel] tcg_qemu_tb_exec...
I'm in qemu-arm. tcg_qemu_tb_exec function is a macro: #define tcg_qemu_tb_exec(env, tb_ptr)\ ((long REGPARM (*)(void *, void *))code_gen_prologue)(env, tb_ptr) #endif I don't understand what function calls. where is code of code_gen_prologue???
[Qemu-devel] arm return
In arm user mode, where does qemu exit? Where is last qemu's instruction?
I.E.
int main (){return 0;}
in what file does qemu run return 0??
[Qemu-devel] arm return
I tried to insert printf(exit\n); , but qemu dosen't write to monitor.
On 06/01/12 13:43, Max Filippov wrote:
On Fri, Jun 1, 2012 at 3:16 PM, Davide Ferraretto
femudevelopm...@gmail.com wrote:
In arm user mode, where does qemu exit? Where is last qemu's instruction?
I.E.
int main (){return 0;}
in what file does qemu run return 0??
Simulated code reaches the point where libc calls 'exit' or 'exit_group' syscall
and then QEMU goes to the do_syscall in the linux-user/syscall.c to terminate
the process.
Re: [Qemu-devel] arm return
I'm in arm user space with sigle step mode. I want write exit\n in
linux shell (no QEMU monitor) when emulate code arrives to return 0
On 06/01/12 14:23, Max Filippov wrote:
On Fri, Jun 1, 2012 at 3:57 PM, Davide Ferraretto
femudevelopm...@gmail.com wrote:
I tried to insert printf(exit\n); , but qemu dosen't write to monitor.
printf should not write to monitor (if you mean QEMU monitor), it
should go to stdout.
I don't have ARM compiler set up ATM, but x86_64 with the following
patch does what I describe:
$ git diff
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 20d2a74..ccb71dc 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -5052,6 +5052,7 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
switch(num) {
case TARGET_NR_exit:
+fprintf(stderr, TARGET_NR_exit\n);
#ifdef CONFIG_USE_NPTL
/* In old applications this may be used to implement _exit(2).
However in threaded applictions it is used for thread termination,
@@ -6833,6 +6834,7 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
#ifdef __NR_exit_group
/* new thread calls */
case TARGET_NR_exit_group:
+fprintf(stderr, TARGET_NR_exit_group\n);
#ifdef TARGET_GPROF
_mcleanup();
#endif
$ cat a.c
#includestdio.h
int main()
{
printf(Hello, world\n);
return 0;
}
$ gcc -static a.c -o a
$ qemu-all/root/bin/qemu-x86_64 ./a
Hello, world
TARGET_NR_exit_group
On 06/01/12 13:43, Max Filippov wrote:
On Fri, Jun 1, 2012 at 3:16 PM, Davide Ferraretto
femudevelopm...@gmail.comwrote:
In arm user mode, where does qemu exit? Where is last qemu's instruction?
I.E.
int main (){return 0;}
in what file does qemu run return 0??
Simulated code reaches the point where libc calls 'exit' or 'exit_group'
syscall
and then QEMU goes to the do_syscall in the linux-user/syscall.c to
terminate
the process.
[Qemu-devel] arm exit code.
In arm user mode, where does qemu exit? Where is last qemu's instruction?
[Qemu-devel] cpsr_write...
Hi!!! 1)How can I use cpsr_write(var, tmp_mask) in qemu- arm(user mode)?? 2)What are var and tmp_mask?? 3)How does QEMU use cpsr register in sigle step mode??
[Qemu-devel] Read location of memory poits esp register
how can I read location of memory poits by esp register (i386 cpu)??
[Qemu-devel] Read location of memory poits esp register
But, I work into qemu code. Is there a c qemu function for this?? On 05/07/12 19:10, Mulyadi Santosa wrote: On Mon, May 7, 2012 at 11:49 PM, Davide Ferraretto femudevelopm...@gmail.com wrote: how can I read location of memory poits by esp register (i386 cpu)?? CMIIW, using gdb stub hooked to Qemu, it should be: p $esp get the number xfrom the number above
Re: [Qemu-devel] [Qemu-discuss] [Qemu-discussion] QEMU via GDB
It dosen't work. GDB returns the same error. - Original Message - From: davide.ferrare...@studenti.univr.it Date: Monday, October 24, 2011 8:37 Subject: Re: [Qemu-discuss] [Qemu-discussion] QEMU via GDB To: davide.ferrare...@studenti.univr.it It dosen't work. GDB return the same error. - Original Message - From: davide.ferrare...@studenti.univr.it Date: Friday, October 21, 2011 16:18 Subject: [Qemu-discuss] [Qemu-discussion] QEMU via GDB To: qemu-disc...@nongnu.org Dear all, I am trying to debug QEMU via GDB. I configured and compiled QEMU with debugging flags, i.e., # CFLAGS=-g3 -O0 ./configure --disable-gfx-check and run gdb: # gdb ./i386-linux-user/qemu-i386 (gdb) break main (gdb) run Starting program: /home/test/femu/i386-linux-user/qemu-i386 Failed to read a valid object file image from memory. Warning: Cannot insert breakpoint 1. Error accessing memory address 0x2f7df: Input/output error. Is there any extra flag to be specified with the GDB for QEMU debugging? I am wondering if the QEMU virtual machine creates any problem to the GDB virtual machine. Thanks.
[Qemu-devel] QEMU via GDB
Dear all, I am trying to debug QEMU via GDB. I configured and compiled QEMU with debugging flags, i.e., # CFLAGS=-g3 -O0 ./configure --disable-gfx-check and run gdb: # gdb ./i386-linux-user/qemu-i386 (gdb) break main (gdb) run Starting program: /home/test/femu/i386-linux-user/qemu-i386 Failed to read a valid object file image from memory. Warning: Cannot insert breakpoint 1. Error accessing memory address 0x2f7df: Input/output error. Is there any extra flag to be specified with the GDB for QEMU debugging? I am wondering if the QEMU virtual machine creates any problem to the GDB virtual machine. Thanks.
