From: asmwarrior <asmwarrior@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit] Improve gdb_realpath for Windows hosts
Date: Tue, 27 Dec 2011 14:12:00 -0000 [thread overview]
Message-ID: <4EF9D06E.7080008@gmail.com> (raw)
In-Reply-To: <20111227124009.GG23376@adacore.com>
Can you explain that why you avoid converting to lowercase?
> /* The file system is case-insensitive but case-preserving.
> So we do not lowercase the path. Otherwise, we might not
> be able to display the original casing in a given path. */
I just thought that lowercase is another canonization of path, so you can have a uniform path when you set breakpoints(file specification)
The original code in iberty library is like:
> /* The MS Windows method. If we don't have realpath, we assume we
> don't have symlinks and just canonicalize to a Windows absolute
> path. GetFullPath converts ../ and ./ in relative paths to
> absolute paths, filling in current drive if one is not given
> or using the current directory of a specified drive (eg, "E:foo").
> It also converts all forward slashes to back slashes. */
> #if defined (_WIN32)
> {
> char buf[MAX_PATH];
> char* basename;
> DWORD len = GetFullPathName (filename, MAX_PATH, buf, &basename);
> if (len == 0 || len > MAX_PATH - 1)
> return xstrdup (filename);
> else
> {
> /* The file system is case-preserving but case-insensitive,
> Canonicalize to lowercase, using the codepage associated
> with the process locale. */
> CharLowerBuff (buf, len);
> return xstrdup (buf);
> }
> }
> #endif
Thanks.
asmwarrior
ollydbg from codeblocks' forum
next prev parent reply other threads:[~2011-12-27 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 17:31 Joel Brobecker
2011-12-22 17:59 ` Eli Zaretskii
2011-12-22 18:16 ` Joel Brobecker
2011-12-27 4:11 ` Checked in: " Joel Brobecker
2011-12-27 12:40 ` asmwarrior
2011-12-27 13:47 ` Joel Brobecker
2011-12-27 14:00 ` asmwarrior
2011-12-27 14:12 ` asmwarrior [this message]
2011-12-27 14:35 ` Joel Brobecker
2011-12-27 16:26 ` asmwarrior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EF9D06E.7080008@gmail.com \
--to=asmwarrior@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox