[Octave-bug-tracker] [bug #57528] imread always fails when Octave was started with the "--traditional" option

[Rik]

Follow-up Comment #2, bug #57528 (project octave):

Tracking this down a bit, the file scripts/image/private/__imread__.m is the
last point in the debug stack which is still an m-file.  The line where the
error is generated is 


  [varargout{1:nargout}] = __magick_read__ (filename, options);


I used the debugger to inspect filename and options variables when octave was
started with --traditional and without.  The variables are the same, so the
problem lies in the C++ code somewhere.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57528>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/