On Sun, Feb 12, 2017 at 5:18 AM, Andriy Tykhonov <[email protected]> wrote: > Ben Coman <[email protected]> writes: > >> Are you on 64-bit using 32-bit Pharo? > > This is not pure 64-bit system. This is multilib setup. So, I can execute > 32-bit and 64-bit programs on the same machine. This is recent system > installation, and Pharo doesn't work well on it. But it did work well on > another Gentoo Linux system with the same multilib support. > >> Can you use ldd to check the pharo binary is linking to these 32-bit >> libraries? >> http://pharo.org/gnu-linux-installation > > $ ldd ./pharo-vm/pharo > > linux-gate.so.1 (0xf76f6000) > libm.so.6 => /lib32/libm.so.6 (0xf7664000) > libdl.so.2 => /lib32/libdl.so.2 (0xf765f000) > libpthread.so.0 => /lib32/libpthread.so.0 (0xf7643000) > libc.so.6 => /lib32/libc.so.6 (0xf7496000) > /lib/ld-linux.so.2 (0xf76f7000)
Okay, so four out of six are obviously bound to 32bit libs. linux-gate seems okay per... http://man7.org/linux/man-pages/man7/vdso.7.html Note that the vDSO that is used is based on the ABI of your user- space code and not the ABI of the kernel. Thus, for example, when you run an i386 32-bit ELF binary, you'll get the same vDSO regardless of whether you run it under an i386 32-bit kernel or under an x86_64 64-bit kerne l. Could you check if ld-linux symlinks to 32-bit location? > > This is mostly the same output (except addresses, such as 0xf76f6000, -- > I'm writing about this fact just because I'm not sure whether it is > important) which I had seen on the previous Gentoo Linux system. > >> >> When you get it working can you provide a recipe for the download page. >> >> Alternatively you might try either (pre-release) 64-bit VM from... >> http://files.pharo.org/vm/pharo-spur64/linux/ >> * pharo-linux-x86_64threaded-201702061308-aa78f27.zip >> * pharo-linux-x86_64itimer-201702030802-61970b6.zip > > I have tried both with the image downloaded from > http://files.pharo.org/image/60/ (Pharo-Image-6.0-latest.zip). > > I get the same result: > > $ ./pharo Pharo-60386.image > This interpreter (vers. 68021) cannot read image file (vers. 6521). > Press CR to quit... > zsh: exit 1 ./pharo ../tmp64/Pharo-60386.image I'm not completely sure, but I think this indicates you're using a 64-bit VM (68021) to open a 32-bit Image (6531). IIUC you need to use Pharo64-60386.image from this zip... However I guess Scale needs FFI and I'm not sure of 64 bit FFI status on Linux. (Esteban?) >> http://files.pharo.org/image/60/ >> * 60385-64.zip >> On Sat, Feb 11, 2017 at 5:49 AM, Andrey Tykhonov <[email protected]> wrote: >>> Hi all, >>> >>>> and which VM do you use (there is a System report browser where you can >>>> find the information. >>> >>> I've somehow managed to get the information from System report browser: >>> >>> Image >>> ----- >>> /home/demi/mess/2017/06/tmp2/Pharo.image >>> Pharo5.0 >>> Latest update: #50768 >>> Unnamed >>> >>> Virtual Machine >>> --------------- >>> /home/demi/mess/2017/06/tmp2/pharo-vm/pharo >>> CoInterpreter VMMaker.oscog-eem.1855 uuid: >>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 >>> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: >>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 >>> https://github.com/pharo-project/pharo-vm.git Commit: >>> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By: >>> Esteban Lorenzano <[email protected]> Jenkins build #589 >>> >>> Unix built on May 4 2016 11:54:41 Compiler: 4.6.3 >>> VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit: >>> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By: >>> Esteban Lorenzano <[email protected]> Jenkins build #589 >>> CoInterpreter VMMaker.oscog-eem.1855 uuid: >>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 >>> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: >>> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 >>> >>> >>> I noticed that there are more items which could be selected (list in the >>> left bar, I mean System report browser), but I cannot get more info, because >>> pharo crashes each time I try to select all text from the all items. May be >>> it would be helpful (and I'll be able to) to get information only from some >>> particular item? But then, I need to know which exactly items would be >>> helpful. >>> >>> Also, I'm attaching to this email log file after execution of the Pharo with >>> strace: >>> >>> strace ./pharo-ui Pharo.image > pharo-ui-with-strace.log 2>&1 >>> >>> I hope it could shed more light on the issue. >>> >>> >
