> > Given how frequent it is for source files to be unavailable,
> > I would say that it would be useful to preserve the GetFullPathName
> > behavior for those files as well, and allow users to set breakpoints
> > without having to worry about how many backslashes GCC has been
> > using. Or said differently, I agree with your decision :-).
> >
> > I am taking a note to:
> >
> >   1. Add an extra comment to this part of the code once you've pushed
> >      your patch;
> >
> >   2. Double-check what newer versions of GCC do. At some point, perhaps
> >      we can declare a minimum GCC version that we fully support and
> >      then mark this code area for possible removal if it ever starts
> >      causing extra work.
> 
> Great, I've pushed them in.

Thank you, Yao. Attached is what I pushed for (1).

For (2), I verified that GCC 4.9 no longer suffers from this problem.
It even looks like it's generating forward slashes, even if the path
to the file given to the compiler itself follows the Windows convention
of backslashes.

gdb/ChangeLog:

        * utils.c (gdb_realpath): Rework comment about handling on
        Windows.

-- 
Joel