All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nuno Silva <nuno.silva@vgertech.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: Matt Zimmerman <mdz@debian.org>,
	user-mode-linux-devel@lists.sourceforge.net,
	224431@bugs.debian.org
Subject: Re: Resolution (Re: [uml-devel] 2.4.22-[67] problems)
Date: Tue, 06 Jan 2004 07:41:39 +0000	[thread overview]
Message-ID: <3FFA66B3.501@vgertech.com> (raw)
In-Reply-To: <200401060258.i062wWFI023087@ccure.user-mode-linux.org>

Hi!

Jeff Dike wrote:
> mdz@debian.org said:
> 
>>It turns out that this problem seems to be due to compiler
>>incompatibility. UML had been built with gcc 2.95 due to old breakage,
>>and when built with gcc 3.3 (as glibc is), everything starts working
>>again.  My suspicion is that this is due to certain recent changes in
>>pthreads.
> 
> 
> Is it your opinion that there's no problem in UML itself?  Having a field
> in the sigcontext getting magically munged is somewhat worrying.  I'd be 
> happier knowing what exactly was happening so I can be sure this wasn't
> exposing some subtle UML bug.
> 

I've been doing some tests and I'd say that the problem is something 
regarding the NPTL+TLS+__thread features of recent libc6 (2.3.2 and 
2.3.3cvs)... But I'm clueless about the fix :-)

I'll setup a chroot where I can play around with glibc setups.

OARS, why does linux (the UML executable) doesn't run under 
/lib/ld-linux.so?

Example:
puma:/tmp# ldd /usr/bin/scp
                 libutil.so.1 => /lib/tls/i686/cmov/libutil.so.1 
(0x4002f000)
         libz.so.1 => /usr/lib/libz.so.1 (0x40032000)
         libnsl.so.1 => /lib/tls/i686/cmov/libnsl.so.1 (0x40044000)
         libcrypto.so.0.9.7 => /usr/lib/i686/cmov/libcrypto.so.0.9.7 
(0x40059000)
         libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0x40156000)
         libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0x4028f000)
         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

puma:/tmp# ldd ./linux
                 libutil.so.1 => /lib/tls/i686/cmov/libutil.so.1 
(0x40018000)
         libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0x4001b000)
         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
puma:/tmp#

scp has a superset of linux's shared libs and runs ok:
puma:/tmp# /lib/ld-linux.so.2 --library-path /lib:/usr/lib /usr/bin/scp
usage: scp [-pqrvBC1246] [-F config] [-S program] [-P port]
            [-c cipher] [-i identity] [-l limit] [-o option]
            [[user@]host1:]file1 [...] [[user@]host2:]file2
puma:/tmp#


But linux does not run:
puma:/tmp# /lib/ld-linux.so.2 --library-path /lib:/usr/lib /tmp/linux
Checking for the skas3 patch in the host...found
Checking for /proc/mm...found
Mapping memory: Invalid argument
puma:/tmp#

If linux could run under ld-linux-so helper testing would be easier :)

Regards,
Nuno Silva






-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-01-06  7:40 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-20  1:13 [uml-devel] 2.4.22-[67] problems Matt Zimmerman
2003-12-20 17:14 ` Jeff Dike
2003-12-21  0:47   ` Matt Zimmerman
2003-12-21 15:58     ` BlaisorBlade
2003-12-21 22:40       ` Matt Zimmerman
2003-12-21 23:16         ` Matt Zimmerman
2003-12-22  0:25           ` Jeff Dike
2003-12-22  4:08             ` Matt Zimmerman
2003-12-22  5:49               ` Daniel Jacobowitz
2003-12-22  9:08                 ` Matt Zimmerman
2004-01-05 17:51                   ` Adam Heath
2004-01-05 18:10                     ` Matt Zimmerman
2003-12-24 12:48         ` BlaisorBlade
2003-12-21  0:52   ` Matt Zimmerman
2003-12-21  1:06     ` Matt Zimmerman
2003-12-28  9:33       ` Matt Zimmerman
2003-12-28  9:51         ` Matt Zimmerman
2003-12-28  9:52           ` Matt Zimmerman
2004-01-06  2:59             ` Jeff Dike
2003-12-28 10:12           ` Matt Zimmerman
2003-12-28 11:30             ` Matt Zimmerman
2003-12-30 18:43               ` Resolution (Re: [uml-devel] 2.4.22-[67] problems) Matt Zimmerman
2004-01-06  2:58                 ` Jeff Dike
2004-01-06  7:41                   ` Nuno Silva [this message]
2004-01-06  8:02                     ` Matt Zimmerman
2004-01-06  8:20                       ` Nuno Silva
2004-01-06  8:47                         ` Nuno Silva
2004-01-06  9:20                     ` Nuno Silva
2004-01-06 17:13                       ` Matt Zimmerman
2004-01-09  7:22                         ` Nuno Silva
2004-01-08  7:07                   ` Matt Zimmerman
2004-01-12 18:36                     ` [uml-devel] Panic with slirp transport and gcc 3.3 Matt Zimmerman
2004-01-13 15:25                       ` [uml-devel] " Bill Allombert
2004-01-13 17:30                         ` Jeff Dike
2004-01-13 17:44                           ` Bill Allombert
2004-01-13 18:51                           ` Matt Zimmerman
2004-01-16  2:38                             ` Jeff Dike
2004-01-16  2:38                               ` Matt Zimmerman
2004-01-16 20:04                                 ` Jeff Dike
2004-01-16 19:49                                   ` Matt Zimmerman
2004-01-17  0:42                                     ` Matt Zimmerman
2003-12-21  1:29   ` [uml-devel] 2.4.22-[67] problems Matt Zimmerman
2003-12-20 19:05 ` Nick Craig-Wood

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=3FFA66B3.501@vgertech.com \
    --to=nuno.silva@vgertech.com \
    --cc=224431@bugs.debian.org \
    --cc=jdike@addtoit.com \
    --cc=mdz@debian.org \
    --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.