octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #43237] line plot fails if a file "x.oct" exis


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #43237] line plot fails if a file "x.oct" exists in the current directory
Date: Tue, 16 Sep 2014 20:01:47 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0

Update of bug #43237 (project octave):

                Category:                Plotting => Interpreter            
              Item Group:                   Crash => Incorrect Result       
                  Status:                    None => Confirmed              
                 Summary: Plotting crashes if a file "x.oct" exists in the
current directory => line plot fails if a file "x.oct" exists in the current
directory

    _______________________________________________________

Follow-up Comment #1:

Thanks for your bug report. I can confirm here, and the error is not actually
caused by your workspace variable named x the same as x.oct. I would say this
is user error, there should not be a file named x.oct in a directory that
Octave can read unless it is a valid compiled oct-file.

First and foremost, do not create files named .oct on your Octave path unless
they are valid oct-files (compiled Octave extension modules). It might be
tempting to use .oct as a data file extension (analogous to .mat for Matlab)
but .oct is actually reserved for compiled code loaded by Octave's
interpreter. If it is not a compiled oct-file, bad things like this may
happen. So the error checking could possible be improved, but this exact
example will probably always cause some kind of error.

The error occurs in a call to cellfun from the plot scripts. The error is more
simply reproduced with:


octave:1> system ("echo > x.oct");
octave:2> cellfun (@(x) x(:), {});
error: caught execution error in library function


If the cellfun call is changed to use "_x" as the lambda argument instead, it
works fine. Or if I create a simple oct-file and compile it as x.oct, the
error goes away also. I'm not sure what the interaction going on beyond this
point is.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?43237>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]