[Top][All Lists]

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

[Octave-bug-tracker] [bug #57528] imread always fails when Octave was st

From: Rik
Subject: [Octave-bug-tracker] [bug #57528] imread always fails when Octave was started with the "--traditional" option
Date: Fri, 3 Jan 2020 16:38:18 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

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:


  Message sent via Savannah

reply via email to

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