From: Christof Schulze <christof.schulze@gmx.net>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] qemu-user-x86_64 segfaults on armv5 (WAS: qemu-user + networking issues / segfaults)
Date: Fri, 06 Sep 2013 23:28:42 +0200 [thread overview]
Message-ID: <14521777.Zs7TYHhG6D@siegfried> (raw)
In-Reply-To: <6220516.fTby4aKWBy@siegfried>
[-- Attachment #1: Type: text/plain, Size: 2549 bytes --]
Hello
Richard, using your vdso patch from today that takes into account vtime
as well, running linux-x86_64 code on arm via qemu-user works! Thank you
very much for your support and energy!
As promised on IRC the software is dead-slow but I do not mind since it
is a batch application anyways.
I only wonder why this is not in the master branch.
Christof
Am Freitag, 6. September 2013, 12:38:21 schrieb Christof Schulze:
> Hello
> Am Mittwoch, 4. September 2013, 08:35:37 schrieb Richard Henderson:
> > On 08/29/2013 02:27 PM, Christof Schulze wrote:
> > > #5 0x6012a100 in tb_gen_code (env=0x612def20, pc=18446744073699066880,
> > > cs_base=0, flags=4243635, cflags=0)
> > > at /mnt/data/build/qemu-1.6.0-ministatic/translate-all.c:964
> > In know exactly what this is -- the fallback vsyscall page.
> > I've had a patch set around for the last three years or so to provide
> > a real vdso for x86_64. I repost it every so often, usually to no
> > response.
> > See git://github.com/rth7680/qemu.git elfload-vdso
> after trying the patch itself and still getting slightly other crashes
> on irc we decided to try this patch based on the master branch. This
> allowed for debugging with gdb as it circumvented a bug of the early
> 1.6rcs of qemu where the g packet was transmitting two many registers.
> Having set a breakpoint at *0x0000000040816725 (the memory position
> where the segfault happens) I got the following
> output.
> Loaded symbols for /lib64/ld-linux-x86-64.so.2
> 0x0000000040802650 in _start () from /lib64/ld-linux-x86-64.so.2
> (gdb) b *0x0000000040816725
> Haltepunkt 1 at 0x40816725: file ../sysdeps/x86_64/dl-trampoline.S, line 46.
> (gdb) cont
> Continuing.
> Breakpoint 1, _dl_runtime_resolve () at ../sysdeps/x86_64/dl-trampoline.S:46
> 46 ../sysdeps/x86_64/dl-trampoline.S: Datei oder Verzeichnis nicht
> gefunden. it says dl-trampoline.S: file or directory not found and gives me
> the gdb shell
> Breakpoint 1, _dl_runtime_resolve () at ../sysdeps/x86_64/dl-trampoline.S:46
> 46 in ../sysdeps/x86_64/dl-trampoline.S
> (gdb)
> Continuing.
> Program received signal SIGSEGV, Segmentation fault.
> 0xffffffffff600400 in ?? ()
> RTH mentioned that the runtime resolution of the symbol was into the
> vsyscall page.
> Now I am unsure where I should go from this point.
> Should I collect more data? If so, what exactly is needed?
> What else could I do to get this resolved?
> Christof
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-09-06 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 22:21 [Qemu-devel] qemu-user + networking issues / segfaults Christof Schulze
2013-08-29 21:27 ` Christof Schulze
2013-09-04 15:35 ` Richard Henderson
2013-09-06 10:38 ` [Qemu-devel] qemu-user-x86_64 segfaults on armv5 (WAS: qemu-user + networking issues / segfaults) Christof Schulze
2013-09-06 21:28 ` Christof Schulze [this message]
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=14521777.Zs7TYHhG6D@siegfried \
--to=christof.schulze@gmx.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).