>>      Vince Berk pointed out what appears to be a thread issue with uml. 
>> The "host" command, part of the bind-utils package, uses threads and crashes 
>> when asked to do anything more complex than show its help screen:
>>
>> -bash-3.1# rpm -q bind-libs bind-utils
>> bind-libs-9.3.3-0.1.rc3.fc6
>> bind-utils-9.3.3-0.1.rc3.fc6
>> -bash-3.1# host www.google.com.
>> Segmentation fault
I believe Jeff is debugging some of these issues.
Thanks for the test case though, couldn't be more simple!


>>      The problem is completely reproducible; the root filesystem and 
>> kernel at http://ford.stearns.org/uml/ give a crash every time you actually 
>> try to look something up with "host".
>>      Should I be talking to the glibc folks about this?
I don't think so, it is probably just a TLS issue in UML.

>       As a side note, if I try to bypass thread support per the 
> instructions at http://dag.wieers.com/howto/compatibility/ , I get a 
> different error (following is with stock "host"):
> 
> -bash-3.1# LD_ASSUME_KERNEL=2.4.19 host www.google.com
> host: error while loading shared libraries: libnsl.so.1: cannot open 
> shared object file: No such file or directory
> 
> -bash-3.1# export LD_ASSUME_KERNEL=2.4.19
> -bash-3.1# strace -f host www.google.com.
> strace: error while loading shared libraries: libc.so.6: cannot open 
> shared object file: No such file or directory
I think that's because glibc 2.5 does not support kernel 2.4, it only 
supports nptl (unfortunately).

Antoine

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Reply via email to