From: Oleg Tolmatcev <oleg.tolmatcev@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: make MSYS path normalization case-insensitive
Date: Sun, 16 Aug 2026 17:59:17 +0200 [thread overview]
Message-ID: <CACcXsZhjXCJ0FVSRZa+s_+eRn1N9-_B3ciuuhE9+ANHC1m5E2g@mail.gmail.com> (raw)
In-Reply-To: <20260804200505.1890-2-oleg.tolmatcev@gmail.com>
вт, 4 авг. 2026 г. в 22:05, Oleg Tolmatcev <oleg.tolmatcev@gmail.com>:
>
> When normalizing Unix-style paths for native MinGW hosts, compare
> MSYS mount prefixes case-insensitively.
>
> This avoids mis-normalizing paths like /C/... by failing to
> match the /c mount point and then falling back to the root
> mount instead.
> ---
> gdb/testsuite/lib/gdb.exp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index 6fb04869605..58f7c54cea0 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -2393,7 +2393,7 @@ proc host_file_normalize_mingw {filename unix_to_win} {
>
> foreach {unix_filename win_filename} $unix_to_win {
> set mount_len [string length $unix_filename]
> - if {[string equal -length $mount_len $unix_filename $filename]} {
> + if {[string equal -nocase -length $mount_len $unix_filename $filename]} {
> if {$unix_filename eq "/"} {
> if {$filename eq "/"} {
> return "$win_filename"
> --
> 2.55.0.windows.3
>
I am dropping this patch. The solution is not to use upper case for
the drive letter when
changing the directory. I can not reproduce it if I do that.
Oleg
prev parent reply other threads:[~2026-08-16 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 20:05 Oleg Tolmatcev
2026-08-16 15:59 ` Oleg Tolmatcev [this message]
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=CACcXsZhjXCJ0FVSRZa+s_+eRn1N9-_B3ciuuhE9+ANHC1m5E2g@mail.gmail.com \
--to=oleg.tolmatcev@gmail.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