From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simon.marchi@polymtl.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 5/5] gdbsupport: add path_join function
Date: Mon, 18 Apr 2022 20:24:15 +0100 [thread overview]
Message-ID: <6c5b669b-45a1-3daf-674b-503ab950c1ff@palves.net> (raw)
In-Reply-To: <c9629980-853e-b284-60d5-f0ad24053b9d@polymtl.ca>
On 2022-04-18 19:11, Simon Marchi via Gdb-patches wrote:
>> Suggest to add a couple of Windows-specific tests here: one which
>> starts with "d:/" instead of just "/", and another with backslashes.
>
> Should these tests only be ran on Windows hosts? In an ideal world,
> this function (and the rest of path handling in GDB) should support
> cross-debugging both ways: GDB on Linux debugging a remote Windows
> program, GDB on Windows debugging a remote Linux program. That means
> corner cases like GDB on Linux should not recognize C:/foo as an
> absolute path when debugging a native Linux program, but it should
> recognize it as an absolute path when debugging a remote Windows
> program. And it should recognize foo\bar\ as ending with a directory
> separator when debugging remotely a Windows program, and not when
> debugging natively. And vice-versa for a Windows GDB / Linux program.
>
> Existing code isn't written with that in mind though (macros like
> IS_DIR_SEPARATOR are host-specific), and I'm not ready to tackle that
> right now. So I've written path_join ignoring those cross-debugging
> scenarios.
>
> So, if I add a test like:
>
> s = ::path_join ("foo\\", "bar", nullptr);
> SELF_CHECK (s == "foo\\bar" || s == "foo/bar");
>
> it won't pass on Linux, as s will be "foo\\/bar". So, as long as
> path_join is host-dependent, I think we'll need to accept that some
> tests will be host-dependent. That's not ideal, but that's how things
> are at the moment.
Note we have:
(gdb) help set target-file-system-kind
Set assumed file system kind for target reported file names.
If `unix', target file names (e.g., loaded shared library file names)
starting the forward slash (`/') character are considered absolute,
and the directory separator character is the forward slash (`/'). If
`dos-based', target file names starting with a drive letter followed
by a colon (e.g., `c:'), are also considered absolute, and the
backslash (`\') is also considered a directory separator. Set to
`auto' (which is the default), to let GDB decide, based on its
knowledge of the target operating system.
(gdb)
This is used in solib.c only currently. Something like "source-file-system-kind"
might make sense to have too. (Not suggesting we add it now.)
next prev parent reply other threads:[~2022-04-18 19:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 20:01 [PATCH 1/5] gdb: call gdb_tilde_expand instead of gdb_tilde_expand_up in source_script_with_search Simon Marchi
2022-04-14 20:01 ` [PATCH 2/5] gdbsupport: make gdb_abspath return an std::string Simon Marchi
2022-04-18 19:41 ` Tom Tromey
2022-04-18 20:09 ` Pedro Alves
2022-04-18 20:11 ` Simon Marchi
2022-04-14 20:01 ` [PATCH 3/5] gdbsupport: make gdb_realpath_keepfile " Simon Marchi
2022-04-18 19:44 ` Tom Tromey
2022-04-14 20:01 ` [PATCH 4/5] gdb: use gdb_tilde_expand instead of gdb_tilde_expand_up in source_script_with_search Simon Marchi
2022-04-18 19:44 ` Tom Tromey
2022-04-18 20:12 ` Simon Marchi
2022-04-14 20:01 ` [PATCH 5/5] gdbsupport: add path_join function Simon Marchi
2022-04-15 5:59 ` Eli Zaretskii
2022-04-18 18:11 ` Simon Marchi
2022-04-18 18:30 ` Eli Zaretskii
2022-04-18 19:24 ` Pedro Alves [this message]
2022-04-15 14:38 ` Lancelot SIX
2022-04-15 16:55 ` Lancelot SIX
2022-04-18 18:43 ` Simon Marchi
2022-04-18 19:09 ` Pedro Alves
2022-04-18 19:12 ` Simon Marchi
2022-04-18 20:55 ` Simon Marchi
2022-04-18 21:07 ` Pedro Alves
2022-04-19 0:19 ` Simon Marchi
2022-04-18 19:22 ` Pedro Alves
2022-04-18 20:01 ` Tom Tromey
2022-04-18 23:11 ` Lancelot SIX
2022-04-20 0:22 ` Simon Marchi
2022-04-18 19:36 ` [PATCH 1/5] gdb: call gdb_tilde_expand instead of gdb_tilde_expand_up in source_script_with_search Tom Tromey
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=6c5b669b-45a1-3daf-674b-503ab950c1ff@palves.net \
--to=pedro@palves.net \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).