Santiago,
I am seeing the same error on Linux and Windows with 4.2.1 and a recent dev.
That message also appears if you try to convert an out-of-range number to a
character (e.g. char(300) or char(-2)). There might be a problem with using
char, unsigned char and signed char inconsistently in the code (probably in
oct-stream.cc).
Can you please open a bug report at
https://savannah.gnu.org/bugs/?group=octave describing your issue?
Markus
--
Sent from: http://octave.1599824.n4.nabble.com/Octave-General-f1599825.html
_______________________________________________
Help-octave mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/help-octave