From: Alexander Graf <agraf@csgraf.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/5] Fix i386 Host
Date: Thu, 17 Jan 2008 10:42:48 +0100 [thread overview]
Message-ID: <478F2318.1030902@csgraf.de> (raw)
In-Reply-To: <20080117132136.09788220.Jens.Arm@gmx.de>
Jens Arm wrote:
> Hi
>
> With this I can compile, but qemu segfaults now when trying to start a ros image:
>
> Starting program: /home/tux/QEMU/qemu -m 192 ros/ros
> [Thread debugging using libthread_db enabled]
> [New Thread -1212344640 (LWP 18268)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1212344640 (LWP 18268)]
> 0x08bcb3b4 in code_gen_buffer ()
> (gdb) bt
> #0 0x08bcb3b4 in code_gen_buffer ()
> #1 0x080de65b in cpu_x86_exec (env1=0x9c497e8) at /home/tux/compile/qemu/cpu-exec.c:679
> #2 0x0805738f in main (argc=119537671, argv=0x20000720) at /home/tux/compile/qemu/vl.c:7445
>
> Any hints?
>
>
Looks like it's still broken. This can only be something minor, as it
did work for me in between, but now I can reproduce you failure here as
well. Stay tuned.
Alex
next prev parent reply other threads:[~2008-01-17 13:23 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 6:42 [Qemu-devel] [PATCH 1/5] Fix i386 Host Alexander Graf
2008-01-17 8:10 ` Alexander Graf
2008-01-17 12:21 ` Jens Arm
2008-01-17 9:42 ` Alexander Graf [this message]
2008-01-17 14:26 ` Alexander Graf
2008-01-17 14:42 ` Johannes Schindelin
2008-01-17 14:47 ` Johannes Schindelin
2008-01-17 15:08 ` Alexander Graf
2008-01-17 15:55 ` Johannes Schindelin
2008-01-18 1:14 ` [Qemu-devel] " consul
2008-01-18 1:22 ` Johannes Schindelin
2008-01-18 2:05 ` Johannes Schindelin
[not found] ` <86022C39-B85C-4769-8ECD-4CB007D82F2E@suse.de>
2008-01-18 12:23 ` Michael Matz
2008-01-18 12:47 ` Johannes Schindelin
2008-01-18 13:12 ` Michael Matz
2008-01-18 13:41 ` Johannes Schindelin
2008-01-18 14:05 ` Michael Matz
2008-01-18 14:22 ` Johannes Schindelin
2008-01-18 14:34 ` Michael Matz
2008-01-18 14:43 ` Johannes Schindelin
2008-01-18 14:54 ` Michael Matz
2008-01-18 15:32 ` Johannes Schindelin
2008-01-18 15:41 ` Michael Matz
2008-01-18 15:51 ` Johannes Schindelin
2008-01-18 15:15 ` Andreas Färber
2008-01-18 6:23 ` Alexander Graf
2008-01-18 13:44 ` Johannes Schindelin
2008-01-18 12:33 ` Alexander Graf
2008-01-17 14:49 ` [Qemu-devel] " Alexander Graf
2008-01-17 15:29 ` Johannes Schindelin
2008-01-17 17:11 ` Andreas Färber
2008-01-17 17:34 ` Alexander Graf
2008-01-17 23:25 ` Andreas Färber
2008-01-18 0:40 ` Mike Kronenberg
2008-01-18 3:07 ` Mike Kronenberg
2008-01-18 12:42 ` Johannes Schindelin
2008-01-18 6:19 ` Alexander Graf
2008-01-18 8:58 ` Andreas Färber
2008-01-18 14:52 ` Andreas Färber
2008-01-17 14:43 ` Jens Arm
2008-01-17 12:44 ` Johannes Schindelin
2008-01-17 13:18 ` Thiemo Seufer
2008-01-17 11:23 ` Johannes Schindelin
2008-01-17 7:54 ` Alexander Graf
2008-01-17 11:40 ` Jens Arm
2008-01-17 12:37 ` Johannes Schindelin
2008-01-17 13:25 ` Johannes Schindelin
2008-01-17 14:27 ` Alexander Graf
2008-01-18 15:41 ` Fabrice Bellard
2008-01-18 15:49 ` Johannes Schindelin
2008-01-18 16:49 ` Alexander Graf
2008-01-18 18:10 ` Johannes Schindelin
2008-01-18 19:08 ` Markus Hitter
2008-01-18 19:28 ` Johannes Schindelin
2008-01-19 8:10 ` Markus Hitter
2008-01-19 11:16 ` Johannes Schindelin
2008-01-19 11:27 ` Markus Hitter
2008-01-19 22:06 ` Johannes Schindelin
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=478F2318.1030902@csgraf.de \
--to=agraf@csgraf.de \
--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).