[Octave-bug-tracker] [bug #64363] [octave forge] (io) xlswrite to existing file fails if temp dir is on different drive

[Philip Nienhuis]

Follow-up Comment #3, bug #64363 (project octave):

@gwiora:
Maybe it isn't 'movefile' but rather the zip function that's at fault, but I
doubt that.

What you can do is enter a 'breakpoint' statement in the file 
private/__OCT_spsh_close__.m  (in the io package subdirectory) just above the
lines where the zip is created (that way search path issues are avoided for
private functions) and try the xlswrite command. It'll stop at the
'breakpoint' statement. From then on 'dbstep' through the file (just use the
buttons in the GUI editor) and inspect if files are created properly. Or
better:
Hint: I usually select (highlight) a statement and press <F9> to execute it
manually, one by one. That way you can avoid being thrown out of debug mode
when an error is hit, and you can also find out exactly which statement
provokes the error (which is otherwise masked because of the try-catch block
around it all).
If it indeed is the 'movefile' function, you can try to mimic the command in a
cmd32 window outside Octave. Maybe the underlying 'move' command in Windows
itself is the culprit.

Anyway this is how I would start tackling this issue. Hopefully it helps you
to debug this further.

BTW I think the SUBST command might merely be some wrapper for the 'net share'
or 'net use' command. Whatever, the resulting drive mapping is the same.


    _______________________________________________________

Reply to this item at:

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

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