[Top][All Lists]

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

[Octave-bug-tracker] [bug #55823] [octave forge] (io) xlsread(...) call

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #55823] [octave forge] (io) xlsread(...) call using OCT interface interferes with GUI editor
Date: Sun, 10 Mar 2019 15:02:12 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48

Follow-up Comment #10, bug #55823 (project octave):

I've tried a little but couldn't come up yet with something. I figured
creating a hierarchy in %TMP% and then debug-stepping through the following

function rmdirtest (tdirname)
  confirm_recursive_rmdir (0, "local");
  rmdir (tdirname, "s");

(where tdirname is obviously the "root" dir in the hierarchy) might trigger
the bug, but no and I have little time now anyway for Octave. I'm busy with it
but progress will be slow.

IIRC there were some bug fixes with files in the editor some weeks or months
ago, could be related. Plus, I have a long series of cross-builds archived
that I can try, usually 3-4 days apart, unfortunately much less "dense" in
last December and January.

My feeling that io itself isn't involved is based on that I never hit this
before (and developing the io package files for OCT interface involved a lot
of debug stepping through __OCT_spsh_close__.m) and it is definitely the
recursive rmdir() statement where it happens.
Also, AFAIU the unzipped spreadsheet file archives aren't locked by e.g.,
unzip (I know, a WAG) as writing to them and zipping works fine.


Reply to this item at:


  Message sent via Savannah

reply via email to

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