Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Sep 2004 10:54:05 -0700
From:      Mike Hunter <mhunter@ack.Berkeley.EDU>
To:        dima <_pppp@mail.ru>
Cc:        freebsd-emulation@freebsd.org
Subject:   ls -l => "unknown system call 229" (was: Re: "cannot execute binary file" and libpthread issues linux+FBSD4.10)
Message-ID:  <20040930175405.GA9747@ack.Berkeley.EDU>
In-Reply-To: <1096447573.649.10.camel@pppp>
References:  <20040928232918.GB14378@ack.Berkeley.EDU> <1096447573.649.10.camel@pppp>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 29, "dima" wrote:

> > In what is a probably unrelated issue, I noticed that linux ls is also
> > dumping core:
> > 
> > #0  0x8814fc09 in ?? ()
> > #1  0x804eb63 in strcpy ()
> > #2  0x804c013 in strcpy ()
> > #3  0x804b65f in strcpy ()
> > 
> > I have linux_base-8 installed...any help?  Save me from having to actually
> > install linux!  :)
> Would you like to try the native ldd?
> It's 4.10 running Oracle-8.1.7:
> $ ldd /usr/oracle/bin/sqlplus
> /usr/oracle/bin/sqlplus:
>         libclntsh.so.8.0 => /usr/oracle/lib/libclntsh.so.8.0
> (0x480cd000)
>         libwtc8.so => /usr/oracle/lib/libwtc8.so (0x48641000)
>         libdl.so.2 => /lib/libdl.so.2 (0x48643000)
>         libm.so.6 => /lib/libm.so.6 (0x48647000)
>         libpthread.so.0 => /lib/libpthread.so.0 (0x48665000)
>         libc.so.6 => /lib/libc.so.6 (0x48678000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x480b8000)
> Maybe the problem is because my Oracle installation was linked @ this
> FreeBSD host against the appropriate *FreeBSD* libraries if possible.

Thanks.  Too bad I can't compare for here since ldd isn't working :(

> Anyway, you can try:
> 1) Run the software from inside the more linux-friendly environment (i
> mean from the linux version of /bin/bash you should have in
> /compat/linux);
> 2) Configure your linux library paths by fixing your
> /compat/linux/etc/ld.so.conf & running /compat/linux/sbin/ldconfig.

Thanks for your advice.  Yes, I have tried running everything from the
/compat/linux/bin/sh (aka bash) shell, but my results are the same.

I don't know what's wrong with my linux library paths, or if there is
anything wrong with them at all.  For me to be getting SIGSYS, it must be
that I'm running code that is for the wrong ABI.  I don't know if that
means there's something that isn't brandelf'd right or if there's some
other bug.  Doing chroot didn't help.

truss /compat/linux/bin/ls -l

...
linux_lstat64(0xbfbff968,0x805a08c,0x881a0b10)   = 0 (0x0)
-- UNKNOWN SYSCALL 229

I saw this post:

http://lists.freebsd.org/pipermail/freebsd-hackers/2003-August/002554.html

So, some system calls not being implemented is a known known?  Am I
screwed or is there something wrong with my seup...It seems unlikely there
are known unimplemented system calls in ls....

I'm going to try going down from linux_base-8 to something else, but I see
a red hat on the horizon (:(

Thanks,

Mike



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040930175405.GA9747>