From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: fix run of 32 bits Linux executables on 64 bits targets
Date: Wed, 10 Oct 2007 19:01:08 +0300 [thread overview]
Message-ID: <f43fc5580710100901m650fc9f0hc96c54fd8091fd06@mail.gmail.com> (raw)
In-Reply-To: <1192002128.9976.186.camel@rapid>
On 10/10/07, J. Mayer <l_indien@magic.fr> wrote:
> Following the patches done for elfload32, it appeared to me that there
> were still problems that would prevent 32 bits executables to run on 64
> bits target in linux user mode emulation.
> First of all, the personality was never set to PER_LINUX32
It's set in elfload32.c, but I think your approach is better. The check for
elf_ex->e_ident[EI_CLASS] == ELFCLASS64
could be moved from elfload32.c.
> The second problem was that pointers used to set the values on the stack
> were still of target_ulong size, which lead 32 bits executable crash
> dereferencing NULL pointers as soon as they wanted to parse their
> arguments.
Nice, I was wondering why my test program crashed.
next prev parent reply other threads:[~2007-10-10 16:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 7:42 [Qemu-devel] RFC: fix run of 32 bits Linux executables on 64 bits targets J. Mayer
2007-10-10 8:18 ` Fabrice Bellard
2007-10-10 16:09 ` Blue Swirl
2007-10-10 17:49 ` Thiemo Seufer
2007-10-10 18:40 ` Fabrice Bellard
2007-10-10 19:02 ` Blue Swirl
2007-10-10 21:51 ` J. Mayer
2007-10-11 15:17 ` Thiemo Seufer
2007-10-11 15:47 ` Blue Swirl
2007-10-11 16:00 ` Thiemo Seufer
2007-10-11 19:26 ` Blue Swirl
2007-10-11 22:00 ` J. Mayer
2007-10-12 16:21 ` Blue Swirl
2007-10-12 18:42 ` Thiemo Seufer
2007-10-12 19:37 ` Blue Swirl
2007-10-12 20:24 ` Thiemo Seufer
2007-10-10 16:01 ` Blue Swirl [this message]
2007-10-10 18:42 ` J. Mayer
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=f43fc5580710100901m650fc9f0hc96c54fd8091fd06@mail.gmail.com \
--to=blauwirbel@gmail.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).