From: "Sven Köhler" <sven.koehler@gmail.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken
Date: Sun, 15 Mar 2009 12:39:34 +0100 [thread overview]
Message-ID: <49BCE8F6.50504@gmail.com> (raw)
In-Reply-To: <49BC2994.6040404@goop.org>
[-- Attachment #1.1: Type: text/plain, Size: 876 bytes --]
Jeremy Fitzhardinge schrieb:
> Has it ever worked? If so, what kernel version did it stop working at?
> Does it fail with all 32-bit executables or just your "hello world"?
I discovered the bug as I tried to compile glibc inside the domU.
glibc's configure tries to compile a test program to determine the
sizeof the long datatype or something simple like that. So at least this
is another program that fails.
I did quick test, whether the empty program (just a main with return 0;
in it) segfaults - but it doesn't segfault. The moment I add a printf,
it segfaults again.
> Can you get a coredump from the fault and see what the faulting
> instruction was?
How do I do that?
Sorry for the stupid question, but unfortunatly this is beyond my
knowledge of the tooldchain :-(
I didn't find any automatically generated file.
Regards,
Sven
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-03-15 11:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gpe0vg$j67$1@ger.gmane.org>
2009-03-13 21:11 ` 2.6.28.7 domU: 32-bit emulation seems to be broken Sven Köhler
2009-03-14 0:38 ` Jeremy Fitzhardinge
2009-03-14 0:59 ` Jeremy Fitzhardinge
2009-03-14 8:48 ` Sven Köhler
2009-03-14 22:03 ` Jeremy Fitzhardinge
2009-03-15 11:39 ` Sven Köhler [this message]
2009-03-15 15:32 ` Jeremy Fitzhardinge
2009-03-15 17:43 ` Sven Köhler
2009-03-15 17:45 ` Jeremy Fitzhardinge
2009-03-15 22:18 ` [Xen-devel] " Sven Köhler
2009-03-15 22:21 ` Sven Köhler
2009-03-15 17:48 ` Jeremy Fitzhardinge
2009-03-15 12:24 ` Sven Köhler
2009-03-15 13:30 ` [Xen-users] " Boris Derzhavets
2009-03-15 15:32 ` Jeremy Fitzhardinge
2009-03-15 16:28 ` Jeremy Fitzhardinge
2009-03-15 17:27 ` [Xen-devel] " Sven Köhler
2009-03-16 20:20 ` Jeremy Fitzhardinge
2009-03-16 20:23 ` Jeremy Fitzhardinge
2009-03-16 22:29 ` Sven Köhler
2009-03-16 22:36 ` Jeremy Fitzhardinge
2009-03-17 14:08 ` Sven Köhler
2009-03-17 16:52 ` Jeremy Fitzhardinge
2009-03-17 20:31 ` [Xen-devel] " Sven Köhler
2009-03-17 21:14 ` Jeremy Fitzhardinge
2009-08-10 11:21 ` Milan Holzäpfel
2009-08-10 12:59 ` Christoph Egger
2009-08-11 7:36 ` Milan Holzäpfel
2009-08-14 20:55 ` Jeremy Fitzhardinge
2009-03-14 9:13 ` [Xen-devel] " Sven Köhler
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=49BCE8F6.50504@gmail.com \
--to=sven.koehler@gmail.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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.