how to discover description of error which terminated run

[Frank Ch. Eigler]

johnlumby wrote:

> [...]  What surprises me is that the run continued for a full 0.1
> seconds (over 4000 lines of output) after this message was logged
> before it shut itself down.  [...]

The intent is not to lose information unnecessarily; the transport of
that queued information is lightweight enough not to cause overload.

>[...] Makes me wonder  -  is there some way of directing error
> messages such as this to some other channel rather than interspersing
> them into the run output.   Or else at least making them more distinctive.

I believe errors/warnings already go to stderr as opposed to stdout.
I opened PR14927 to make them even more visible.  (Want to give coding
that up a try?  We'll help!)


- FChE