From: Michael L Torrie <torriem@chem.byu.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] segfault in current cvs
Date: Tue, 06 Jan 2004 18:13:31 -0700 [thread overview]
Message-ID: <1073438011.4352.2.camel@isengard> (raw)
In-Reply-To: <20040106202937.GP3483@suse.de>
On Tue, 2004-01-06 at 13:29, Jens Axboe wrote:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 15913)]
> cpu_x86_exec (env1=0x0) at /home/axboe/qemu-cvs/cpu-exec.c:323
> 323 tb->cs_base = (unsigned long)cs_base;
> (gdb) p tb
> $1 = (TranslationBlock *) 0x0
> (gdb) p cs_base
> $2 = (uint8_t *) 0x0
> (gdb)
>
This is the same segfault I get when running ordinary x86 linux binaries
on my ppc yellowdog box. I hope we can find a solution to this problem.
Michael
> which looks odd, given the !tb check just a few lines up. I'm using:
>
> axboe@apu:/home/axboe $ gcc --version
> gcc (GCC) 3.3.3 20031229 (prerelease) (Debian)
--
Michael L Torrie <torriem@chem.byu.edu>
next prev parent reply other threads:[~2004-01-07 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 20:29 [Qemu-devel] segfault in current cvs Jens Axboe
2004-01-06 21:39 ` Fabrice Bellard
2004-01-07 9:17 ` Jens Axboe
2004-01-07 1:13 ` Michael L Torrie [this message]
2004-01-07 2:53 ` Michael Torrie
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=1073438011.4352.2.camel@isengard \
--to=torriem@chem.byu.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.