@Dennis thanks again!

@Dennis I've noticed that when an Octave (or MATL) program expects input from STDIN and there is none, an error message occurs in STDOUT (not just in STDERR). This didn't use to happen. Did you change something that might be the reason for that? The error sounds like C++. Here's and example.

I'm asking because the standard way to generate test suites in MATL is an infinite loop that keeps requesting input there's no input, and then it exits with error. In the past, only the error message in STDERR would appear

Example with MATL

That's a change in glibcxx. The new version that comes with Fedora 28 treats out-of-bound errors as fatal.

Ah, I see. So it can't be avoided?

No biggie. The test suites will have to use a finite loop

As far as I know, there's no straightforward way to avoid it.

Ok, thanks for the quick response!

How are things going in your place? Do you have classroom holidays this time of the year?

Sort of. There are no classes during the examination period.

@LuisMendo I might be able to send the error message to STDOUT. Would that help?

@Dennis You mean STDERR, right? Yes, that's great. That way the error doesn't distract from the wanted output in STDOUT. Thanks for taking the time!

Since this affects everything written in C++, I might as well enable it for everything. Hopefully, that won't cause any issues.