Thanks for that data point, Thierry! On 19 July 2017 at 14:29, Thierry Goubier <[email protected]> wrote:
> Hi Luke, > > I'm using OSProcess for my day to day development work in 64bits on the > snap and default pharo vms, and it works. > > Regards, > > Thierry > > > 2017-07-19 14:25 GMT+02:00 Luke Gorrie <[email protected]>: > >> Hoi, >> >> Does OSProcess work for other people with a 64-bit Linux VM? >> >> I am seeing strange errors specifically when I build in 64-bit mode: >> Processes always immediately print an obscure error and exit with status >> 127. >> >> The error is printed by the child process. It seems to contain some >> control characters, or a funky text encoding, and a large number for its >> error code. >> >> [pid 19070] writev(2, [{"/bin/sh", 7}, {": ", 2}, {" \n\2303\374\177", >> 6}, {": ", 2}, {"", 0}, {"", 0}, {"\270\271\247\336;\177", 6}, {": ", 2}, >> {"Error 18446744073136382760", 26},\ >> {"\n", 1}], 10) = 52 >> >> More complete strace output in this gist: https://gist.github.com/ >> 81ca7b1c6b8cc412b66951bb6d57e1ea >> >> Reproduce with e.g. OSProcess command: 'pwd' (it doesn't seem to matter >> what command is chosen.) >> >> Anybody else see this / not see this? Any ideas? >> >> Could be that some of the magic in the UnixOSProcessPlugin fork method is >> not working on 64-bit or with my toolchain...? >> >> >> >
