From: Christian Biesinger <cbiesinger@google.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] testsuite: use cygpath to convert from Unix to Windows paths
Date: Wed, 11 Mar 2020 13:40:22 -0500 [thread overview]
Message-ID: <CAPTJ0XHvyrOEjHNj2eeOECNCB6a-E1VmzCuptT30RicgDLeHJw@mail.gmail.com> (raw)
In-Reply-To: <20200311183212.28601-1-simon.marchi@efficios.com>
On Wed, Mar 11, 2020 at 1:32 PM Simon Marchi via Gdb-patches
<gdb-patches@sourceware.org> wrote:
>
> When on a MinGW host, standard_output_file uses a regular expression to
> convert Unix-style paths of the form "/c/foo" to "c:/foo". This is
> needed because the paths we pass to GDB (for example, with the "file"
> command) need to be in the Windows form.
>
> However, the regexp only works if your binutils-gdb repo is under a
> `/[a-z]/...` path (the Unix paths mapping to Windows drives).
> Presumably, that works if you clone the repo in Windows, then access it
> through `/c/...`.
>
> In my case, I've cloned the repository directly inside my MinGW shell,
> so in /home/smarchi. The regexp therefore doesn't work for me. The
> path doesn't get transformed, and the file command fails when running
> any test:
>
> (gdb) file /home/smarchi/build/binutils-gdb/gdb/testsuite/outputs/gdb.arch/i386-bp_permanent/i386-bp_permanent
> /home/smarchi/build/binutils-gdb/gdb/testsuite/outputs/gdb.arch/i386-bp_permanent/i386-bp_permanent: No such file or directory.
>
> A safer way to do this conversion would be to use the cygpath utility.
> It can be used to convert any MinGW path into its Windows equivalent.
>
> Note that despite originally coming from Cygwin, the cygpath utility is
> distributed by mingw-w64 and can be used in that environment.
>
> With this, the file command in the test succeeds:
>
> (gdb) file C:/msys64/home/smarchi/build/binutils-gdb/gdb/testsuite/outputs/gdb.arch/i386-bp_permanent/i386-bp_permanent
> Reading symbols from C:/msys64/home/smarchi/build/binutils-gdb/gdb/testsuite/outputs/gdb.arch/i386-bp_permanent/i386-bp_permanent...
>
> gdb/testsuite/ChangeLog:
>
> * lib/gdb.exp (standard_output_file): Use cygpath to convert
> from Unix to Windows path.
> ---
> gdb/testsuite/lib/gdb.exp | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index 9614e8dc87cd..ac16e0e85c99 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -4899,8 +4899,10 @@ proc standard_output_file {basename} {
> file mkdir $dir
> # If running on MinGW, replace /c/foo with c:/foo
> if { [ishost *-*-mingw*] } {
> - set dir [regsub {^/([a-z])/} $dir {\1:/}]
> + set dir [exec cygpath --mixed "${dir}"]
This is fine, but out of curiosity, why --mixed instead of --windows?
> +
> }
Why the empty line above?
> +
> return [file join $dir $basename]
> }
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2020-03-11 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 18:32 Simon Marchi
2020-03-11 18:40 ` Christian Biesinger [this message]
2020-03-11 19:09 ` Simon Marchi
2020-03-11 19:14 ` Eli Zaretskii
2020-03-11 19:26 ` Simon Marchi
2020-03-13 17:57 ` Tom Tromey
2020-03-13 18:14 ` Christian Biesinger
2020-03-13 19:11 ` Tom Tromey
2020-05-12 22:44 ` Simon Marchi
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=CAPTJ0XHvyrOEjHNj2eeOECNCB6a-E1VmzCuptT30RicgDLeHJw@mail.gmail.com \
--to=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
/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