Hi Thierry, On Wed, Jul 19, 2017 at 04:01:46PM +0200, Thierry Goubier wrote:
Hi Alistair,
OSProcess use of ifNotNilDo: will simply get rewritten on the fly when you load it via Metacello.
This doesn't work in Pharo 7 because the methods are no longer present (thus the re-write rule isn't present). Cheers, Alistair
Thierry
2017-07-19 15:56 GMT+02:00 Alistair Grant <akgrant0710@gmail.com>:
Hi Luke,
On Wed, Jul 19, 2017 at 02:25:55PM +0200, Luke Gorrie wrote: > 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...?
I wanted to try and reproduce this with my locally built VM but can't even load OSProcess because it is using the deprecated message #ifNotNilDo:.
I'm currently loading OSProcess using:
Metacello new configuration: 'OSProcess'; version: #stable; repository: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo50/ main'; load.
Would you please let me know how you load OSProcess?
Thanks, Alistair