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

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

[Octave-bug-tracker] [bug #43979] test unpack fails in MXE-Octave ver 4.


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #43979] test unpack fails in MXE-Octave ver 4.1.0+
Date: Sun, 11 Jan 2015 21:42:16 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30

Update of bug #43979 (project octave):

                  Status:                    None => Confirmed              
                 Summary: test unapck fails in MXE-Octave ver 4.1.0+ => test
unpack fails in MXE-Octave ver 4.1.0+

    _______________________________________________________

Follow-up Comment #1:

Thanks for the report.

Confirmed on 4.1.0+ & 3.9.0+

After stepping through the code I think the culprit is the call (at L.147) to
canonicalize_file_name. That function converts native Windows backslash
fileseps into forward slashes.

A similar alternative function (make_absolute_filename) leaves the file
separators intact; but it has to be tested on Linux as well before that change
can be made safely; as there seem to be some subtle differences between
canonicalize_file_name and make_absolute_filename.  I had earlier discussion
on this subject some years ago as regards drive letters on Windows (I see no
unpack tests for that BTW), see here: https://savannah.gnu.org/bugs/?36677

Even then the test (first assert in unwind_protect block) fails for me:

>>   assert (filelist{1}, filename);

error: ASSERT errors for:  assert (filelist {1},filename)

  Location  |  Observed  |  Expected  |  Reason
     []      C:\Users\philip\AppData\Local\Temp\oct-31\oct-32
      C:\Users\philip\AppData\Local\Temp\oct-32                 Strings don't
match



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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