bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/29533] New: binutils 2.39 no longer works with UNC paths


From: brecht at sanders dot org
Subject: [Bug binutils/29533] New: binutils 2.39 no longer works with UNC paths
Date: Sun, 28 Aug 2022 13:57:59 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=29533

            Bug ID: 29533
           Summary: binutils 2.39 no longer works with UNC paths
           Product: binutils
           Version: 2.39
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: brecht at sanders dot org
  Target Milestone: ---

In https://sourceware.org/bugzilla/show_bug.cgi?id=25713 code was changed in
_bfd_real_fopen() in bfd/bfdio.c to handle long path names in Windows.

This was done by prepending pefix "\\?\" to the path.

Unfortunately this breaks using UNC network paths (\\server\share).
Looking at
https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry
it probably also breaks relative paths and paths containing . or .. as
references to the current/parent directory.

So it looks like the patch from
https://sourceware.org/bugzilla/show_bug.cgi?id=25713 is incomplete and should
be modified to at least also support UNC paths.

I'm not the only one with this issue, see also:
https://github.com/brechtsanders/winlibs_mingw/issues/112

Also, from a performance point of view, I don't see the point in converting the
path to UTF16 and using the wide path (as done in _bfd_real_fopen() in
bfd/bfdio.c). Is this necessary or is there any added benefit in doing so?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

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