Thu 10 Sep 2015 11:55:59 PM UTC, original submission:
Hello,
I am using Octave to interpret the following script (b/w but not including the tilde-fences):
~~~
A = [1 0 1 1 0;
1 1 1 0 0;
0 1 1 1 1;
1 1 0 0 1];
x = [1 0 1 1 0]';
mod(A*x, 2)
~~~
When I don't use the "--traditional" option it gives the correct output and then exits without error.
When I do use the "--traditional" option, it gives correct output but then hangs. When I try to kill it with Control-C nothing happens until I press the Enter key. After I press the Enter key, the following message is printed to stderr:
~~~
error: fatal flex scanner internal error--end of buffer missed
fatal flex scanner internal error--end of buffer missed
panic: Segmentation fault -- stopping myself...
~~~
When I run "$ octave --traditional" without specifying a script to run, it behaves correctly: this problem only occurs when I specify a script using something like "$ octave --traditional ./script.m"
I suspect this might actually be two bugs in one: --traditional has problems interpreting scripts, and the flex parser has problems understanding Control-C.
The operating system is Arch Linux.
Please let me know if you require any more information or if there is any other way I can assist in solving this problem.
|