UNC Pathname handling

Alexandre Hardy alexandre.hardy at gmail.com
Fri Dec 11 03:03:25 CST 2009

Hi Paul,

Stupid question: What do you mean by bottom post? I have
added wine-devel as a CC to these messages, is that

According to my log it seems to be a GetLongPathNameW.

GetLongPathNameA does not exhibit the same problems
as GetLongPathNameW. So GetLongPathNameA(path, NULL, 0)
succeeds, while GetLongPathNameW(path, NULL, 0) segfaults.
This is because GetLongPathNameA provides its own not NULL
buffer to GetLongPathNameW.

It also seems to me that only GetLongPathNameW is required to
handle UNC pathnames that begin with '\\?\' (at least, that
is how I understand the MSDN).

Kind regards

On Fri, Dec 11, 2009 at 10:56 AM, Paul Vriens
<paul.vriens.wine at gmail.com> wrote:
> Hi Alexandre,
> On 12/11/2009 09:49 AM, Alexandre Hardy wrote:
>> Hi Paul,
>> I guess it could fall under bug #19807. I was actually testing it with
>> Nokia Ovi Installer.
> (Please bottom post on wine-devel).
> So to fix 19807 you need to handle the '\\?\' cases only so it seems?
> Remember that GetLongPathNameA is forward to GetLongPathNameW and from the
> bug report one can't see which one is actually called. So you need a log
> file with either a +file trace or change the TRACE() in GetLongPathNameA to
> a FIXME().
> --
> Cheers,
> Paul.

Alexandre Hardy

More information about the wine-devel mailing list