On Wed, Mar 28, 2007 at 09:25:13PM +0200, Loic Hoguin wrote:
> Hello,
> 
> On Wed, 28 Mar 2007 12:01:41 +0200, Nicolas Joly <njoly@pasteur.fr> wrote:
> >As Blair said, 64bit binaries needs to be in `/emul/linux' subtree,
> >and 32bit in `/emul/linux32'.
> 
> Yes, that was that.
> 
> Right now opera doesn't work yet (since it needs a few more libraries
> currently unavailable) but the binary is executed successfully.

Great.

> >>And another thing came up: I cannot use most of the binaries that came
> >>with linux (64 bit) emulation too. Most core dump (the kdump for 64bit
> >>Linux date is attached).
> >
> >I did not see anything obvious with your trace. Can you try to modify
> >emul.linux.kern.osrelease to emulate a 2.6 Linux kernel ?
> >
> >njoly@lanfeust [~]> sysctl emul
> >emul.linux.kern.ostype = Linux
> >emul.linux.kern.osrelease = 2.6.22
> >emul.linux.kern.osversion = #0 Wed Feb 20 20:00:02 CET 2002
> >emul.linux32.kern.ostype = Linux
> >emul.linux32.kern.osrelease = 2.4.18
> >emul.linux32.kern.osversion = #0 Wed Feb 20 20:00:02 CET 2002
> 
> Hm this didn't work. It is crashing exactly the same way.
> By the way the 32bit one's are not crashing.
> 
> The weird thing is that 64bit bash is not crashing, but 64bit ls or
> date do. Should I submit a PR about this?

I as able to reproduce the problem on a friend laptop (Sony VAIO with
Intel Core 2 CPU) ... In the mean time, no problem on my workstation
(Tyan S2885 with 2 Opterons 246 CPUs).

A simple test program only calling getpid() works if statically
linked, but crash otherwise.

Can you post your machine dmesg ?

-- 
Nicolas Joly

Biological Software and Databanks.
Institut Pasteur, Paris.