[Vm-dev] OSProcess fork issue with Debian built VM

Max Leske maxleske at gmail.com
Wed May 17 15:13:27 UTC 2017


Hi Alistair,

> On 17 May 2017, at 17:06, vm-dev-request at lists.squeakfoundation.org wrote:
> 
> Hi Max,
> 
> On Wed, May 17, 2017 at 02:36:27PM +0200, Max Leske wrote:
>>    On 17 May 2017, at 14:00, vm-dev-request at lists.squeakfoundation.org <mailto:vm-dev-request at lists.squeakfoundation.org> wrote:
>> 
>>    I'm seeing the same behaviour as you, i.e. OSProcess works in a VM
>>    downloaded from get.pharo.org <http://get.pharo.org/>, but locks up when using the VM I
>>    compiled.
>> 
>>    Both VMs (threaded heartbeat) are based on the same source code, i.e.:
>> 
>>    VM: 201705022326 https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $
>>    Date: Tue May 2 16:26:41 2017 -0700 $
>> 
>>    I'll try and take a look at this eventually, but I'm not sure how long
>>    that will be (several weeks away, at least).
>> 
>>    If you figure it out, please let me know.
>> 
>> 
>> Thanks Alistair. Can you tell me which library versions you're linking against
>> at build time?
> 
> I'm not sure exactly what info you're after, let me know if it isn't
> included below...
> 
> OS: Ubuntu 16.04.2
> 
> $ uname -a
> Linux alistair-xps13 4.8.0-51-generic #54~16.04.1-Ubuntu SMP Wed Apr 26
> 16:00:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> 
> $ ldd pharo
> 	linux-gate.so.1 =>  (0xf7707000)
> 	libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf76f0000)
> 	libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf76d3000)
> 	libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf767d000)
> 	libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf74c7000)
> 	/snap/pharo/current/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x56572000)
> 
> 
> OSProcessAccessor forThisOSProcess primOSProcessPluginModuleVersionString
> "'4.3.3 Cog'"
> 
> OSProcessAccessor forThisOSProcess primOSProcessPluginModuleName
> "'UnixOSProcessPlugin VMConstruction-Plugins-OSProcessPlugin.oscog-eem.54 (i)'"

Thanks. Could you also perform the equivalent of "sudo apt-cache policy libc6" for those libraries? That should give you something like

libc6:
  Installed: 2.19-18+deb8u7
  Candidate: 2.19-18+deb8u9
  Version table:
     2.19-18+deb8u9 0
        500 http://ftp.debian.org/debian/ jessie/main amd64 Packages
 *** 2.19-18+deb8u7 0
        100 /var/lib/dpkg/status
     2.19-18+deb8u3 0
        500 http://security.debian.org/ jessie/updates/main amd64 Packages

That way I can see which exact versions of the libraries you are using (as you can see I have 2.19 while the travis job links agains 2.15).

Cheers,
Max

> 
> Cheers,
> Alistair

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20170517/47a62ef3/attachment.html>


More information about the Vm-dev mailing list