[Vm-dev] [OpenSmalltalk/opensmalltalk-vm] Provide control over VM messages (#275)
notifications at github.com
Wed Aug 8 19:26:39 UTC 2018
On Wed, Aug 8, 2018 at 9:29 AM, Damien Pollet <notifications at github.com>
> Could the VM provide an option for separating its own output from the
> image's output?
Yes, I guess it could. But (to state the obvious) this wouldn't help e.g.
errors coming from C library code, only explicit error messages from the VM
> 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 hpi-swa/smalltalkCI#388
The thing is, this is worrying. If pthread_setschedparam complains then it
likely means you don't have reliable time or delays in the running system.
You may be better off using an timer heartbeat VM if your build machine
won't support multiple thread priorities. Alternatively it could simply be
a issue of the age of the kernel.
Can you post the exact error message and the build machine's kernel version?
> 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.
Yes, but this would require some intelligence to ensure the VM does answer
actual stderr through the primitives that provide access to them
(stdioHandles uses the primitiveFileStdioHandles primitive in
FilePlugin). So it's not trivial.
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/275>, or mute
> the thread
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev