From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Fragile MAX_OP_PER_INSTR
Date: Tue, 22 Apr 2008 12:19:06 +0200 [thread overview]
Message-ID: <480DBB9A.2050905@siemens.com> (raw)
Hi,
we ran into a weird SEGFAULT of QEMU which turned out to be a corruption
of tcg_ctx due to writing beyond gen_opc_buf. The reason for this was a
too small MAX_OP_PER_INSTR, given a particular toolchain (here the one
of SLES 10 for x86-32). So far it runs fine with
#define MAX_OP_PER_INSTR 64
Does anyone have an idea how to resolve the related comment in exec-all.h?
/* XXX: make safe guess about sizes */
Or should we just increase the safety margin?
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next reply other threads:[~2008-04-22 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 10:19 Jan Kiszka [this message]
2008-05-06 12:39 ` [Qemu-devel] Fragile MAX_OP_PER_INSTR Edgar E. Iglesias
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=480DBB9A.2050905@siemens.com \
--to=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).