[Octave-bug-tracker] [bug #45816] canonicalize_file_name() changed behavoir between 3.8.2 and 4.0.0 on windows

[Philip Nienhuis]

Update of bug #45816 (project octave):

                  Status:                    None => Confirmed              
                 Release:                   4.0.0 => dev                    

    _______________________________________________________

Follow-up Comment #2:

(Too bad I hadn't noted this issue before I fixed bug #43979)

@Rik:
I've built Octave cf. your instructions. Indeed, cstdlib is included a few
lines higher up in file-ops.cc.

But alas, it didn't help - the bug is still there.

I had a brief look in the gnulib repo where canonicalize.* live
(http://git.savannah.gnu.org/cgit/gnulib.git/tree/lib). It seems the last real
code changes (apart from copyright updates) that affect their behavior date
from December 2012 (canonicalize-lgpl from 2013 but only for Solaris).
Octave-3.8.2 was released in summer 2014.
As both Octave-3.8.2 and 4.0.0 are from (much) later than the latest real code
changes in the canonicalize*.* files in gnulib, but behave differently, my
conclusion is that the issue must lie within Octave itself.

I'm not familiar with gdb (and the next weeks I lack time to dive into it);
yet for those who are familiar with gdb and want to help I have an MXE
Octave-4.1.0+ build f. 64-bit Windows with unstripped Octave in my Dropbox,
the link is in patch #8656 comment #36. (Note that the dependencies are
stripped.)
That snapshot was made for Michael Barnes (the variable editor "dev"), but to
help solve this bug I'll wait a little longer with wiping that version from
Dropbox - normally I'm not so in favor of distributing development snapshots.

Release => dev

    _______________________________________________________

Reply to this item at:

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

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