From: Ulrich Hecht <uli@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Porting QEMU to Minix - op_goto_tb1 segfaults because tb_next[1] is NULL
Date: Thu, 23 Aug 2007 11:37:27 +0200 [thread overview]
Message-ID: <200708231137.28138.uli@suse.de> (raw)
In-Reply-To: <000301c7e4eb$24b81600$0200a8c0@Feanor>
On Wednesday 22 August 2007, Erik van der Kouwe wrote:
> My problem is the following: quickly after starting I get a
> segmentation fault while the generated code is running.
>
> This happens in the code generated from op_goto_tb1 and is caused by
> jumping to a NULL pointer. This NULL pointer originates from the
> tb_next[1] field of the translation block data structure passed as a
> parameter. I have verified in the disassembler that the parameter in
> the generated code is processed correctly and the field is indeed
> tb_next[1].
I had a similar problem when fixing S/390 hosts. IIRC it was caused by
the "portable" GOTO_TB macro. On translation the goto is patched to jump
out of the block, which is something the compiler does not reckon with.
You may want to disassemble it and check if registers are overwritten
before the jump takes place.
CU
Uli
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2007-08-23 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 18:34 [Qemu-devel] Porting QEMU to Minix - op_goto_tb1 segfaults because tb_next[1] is NULL Erik van der Kouwe
2007-08-23 9:37 ` Ulrich Hecht [this message]
2007-08-23 19:38 ` [Qemu-devel] Porting QEMU to Minix - op_goto_tb1 segfaultsbecause " Erik van der Kouwe
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=200708231137.28138.uli@suse.de \
--to=uli@suse.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).