From: Nuno Silva <nuno.silva@vgertech.com>
To: "La Monte H.P. Yarroll" <piggy@timesys.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML running on host-kernel 2.6.0 with NPTL-enabled glibc problem
Date: Fri, 09 Jan 2004 13:35:38 +0000 [thread overview]
Message-ID: <3FFEAE2A.4030700@vgertech.com> (raw)
In-Reply-To: <3FFEAA6C.8020002@timesys.com>
La Monte H.P. Yarroll wrote:
>
>
> The calls set_thread_area(2) and get_thread_area(2) are not implemented
> in UML.
> Both are essential to NPTL. There may be other problems too...
>
> Implementing them gets really tricky if you want UML to work with a
> 2.4.x host.
> I've been trying to steal enough cycles to learn enough to just
> implement them on a 2.6.0 host.
>
Hi!
You're talking about running nptl enabled glibc inside UML, aren't you?
I'm talking about the host. Any host with kernel 2.6 and glibc-nptl-tls
makes the uml executable segfault very early (see the link in my
previous message for strace and gdb output.
Quick description:
-----
puma:/uml# ./linux
Checking for the skas3 patch in the host...found
Checking for /proc/mm...found
[1]+ Stopped ./linux
puma:/uml# fg
./linux
Segmentation fault
puma:/uml# ldd linux
linux-gate.so.1 => (0xffffe000)
libutil.so.1 => /lib/libutil.so.1 (0x40019000)
libc.so.6 => /lib/libc.so.6 (0x4001c000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
puma:/uml# uname -a
Linux puma 2.6.0 #2 Mon Jan 5 09:25:45 WET 2004 i686 unknown unknown
GNU/Linux
-----
Or did I miss anything in your explanation?
Regards,
Nuno Silva
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-01-09 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 9:09 [uml-devel] UML running on host-kernel 2.6.0 with NPTL-enabled glibc problem Nuno Silva
2004-01-09 13:19 ` La Monte H.P. Yarroll
2004-01-09 13:29 ` La Monte H.P. Yarroll
2004-01-09 13:39 ` Nuno Silva
2004-01-09 13:35 ` Nuno Silva [this message]
2004-01-10 20:25 ` Oleg Drokin
2004-01-11 10:49 ` BlaisorBlade
2004-01-11 18:28 ` Oleg Drokin
2004-01-12 3:49 ` Nuno Silva
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=3FFEAE2A.4030700@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=piggy@timesys.com \
--cc=user-mode-linux-devel@lists.sourceforge.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 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.