[Vm-dev] [OpenSmalltalk/opensmalltalk-vm] Provide control over VM messages (#275)

Damien Pollet notifications at github.com
Wed Aug 8 16:29:07 UTC 2018


Could the VM provide an option for separating its own output from the image's output?

Concretely, the VM complains about pthread_setschedparam in my Travis builds, which prevents writing command-line scripts with clean output both on stdout and stderr. See https://github.com/hpi-swa/smalltalkCI/issues/388

Maybe it's possible to play with the file descriptors at image startup, but it would make sense if the VM itself had something like a `--silent` or a `--vm-stderr FILE` flag (the JVM has `-Xlog`) to redirect its diagnostic messages so that anything that goes to stdout or stderr exclusively comes from the image.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/275
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20180808/587d18c1/attachment.html>


More information about the Vm-dev mailing list