From: TeLeMan <geleman@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] "cpu-exec.c: avoid AREG0 use" breaks x86 emulation on x86-64
Date: Fri, 1 Jul 2011 09:44:46 +0800 [thread overview]
Message-ID: <BANLkTi=Unfpkty5TYVUvJEBp1hzbN4du=g@mail.gmail.com> (raw)
In-Reply-To: <4E0CA885.2050308@siemens.com>
On Fri, Jul 1, 2011 at 00:47, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> Hi Blue,
>
> commit cea5f9a28f breaks here, just starting qemu without any
> parameters:
>
> Starting program: qemu-system-x86_64
> [Thread debugging using libthread_db enabled]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff39ac770 in __sigsetjmp () from /lib64/libc.so.6
> (gdb) bt
> #0 0x00007ffff39ac770 in __sigsetjmp () from /lib64/libc.so.6
> #1 0x00000000004eb96c in cpu_x86_exec (env=0x11d09a0) at cpu-exec.c:233
> #2 0x000000000040f056 in tcg_cpu_exec (env=0x11d09a0) at cpus.c:1059
> #3 cpu_exec_all () at cpus.c:1100
> #4 0x000000000058cfcb in main_loop () at vl.c:1380
> #5 main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at vl.c:3318
>
> Please have a look.
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT T DE IT 1
> Corporate Competence Center Embedded Linux
>
>
It works on gcc 4.4.5 x64. Which version is your gcc?
next prev parent reply other threads:[~2011-07-01 1:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 16:47 [Qemu-devel] "cpu-exec.c: avoid AREG0 use" breaks x86 emulation on x86-64 Jan Kiszka
2011-06-30 21:17 ` Stefan Weil
2011-07-01 1:44 ` TeLeMan [this message]
2011-07-01 20:15 ` Blue Swirl
2011-07-02 7:50 ` [Qemu-devel] [PATCH] tcg: Reload local variables after return from longjmp Jan Kiszka
2011-07-02 9:08 ` Blue Swirl
2011-07-02 9:43 ` Jan Kiszka
2011-07-03 14:09 ` Paolo Bonzini
2011-07-12 20:56 ` Blue Swirl
2011-08-11 11:30 ` Peter Maydell
2011-08-11 12:16 ` Paolo Bonzini
2011-08-11 12:40 ` Peter Maydell
2011-08-11 13:13 ` Paolo Bonzini
2011-08-11 13:31 ` Peter Maydell
2011-08-11 14:10 ` Paolo Bonzini
2011-08-11 14:12 ` David Gilbert
2011-08-11 14:24 ` Peter Maydell
2011-08-11 14:32 ` Paolo Bonzini
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='BANLkTi=Unfpkty5TYVUvJEBp1hzbN4du=g@mail.gmail.com' \
--to=geleman@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=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).