From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Fix lookup of separate debug file on MS-Windows
Date: Thu, 18 Apr 2019 13:49:00 -0000 [thread overview]
Message-ID: <83ef5ze84y.fsf@gnu.org> (raw)
If you put the separate debug file in a global debug directory, GDB on
MS-Windows will currently fail to find it. This happens because we
obtain the directory to look up the debug file by concatenating the
debug directory name with the leading directories of the executable,
and the latter includes the drive letter on MS-Windows. So we get an
invalid file name like
d:/usr/lib/debug/d:/usr/bin/foo.debug
The patch below fixes that:
--- gdb/symfile.c~0 2019-03-27 00:52:05.000000000 +0200
+++ gdb/symfile.c 2019-04-18 13:19:05.231697600 +0300
@@ -1443,6 +1443,18 @@ find_separate_debug_file (const char *di
= dirnames_to_char_ptr_vec (debug_file_directory);
gdb::unique_xmalloc_ptr<char> canon_sysroot = gdb_realpath (gdb_sysroot);
+ /* MS-Windows/MS-DOS don't allow colons in file names; we must strip
+ the drive letter, so that the file name resulting from splicing
+ below will be valid. */
+ if (HAS_DRIVE_SPEC (dir_notarget))
+ {
+ dir_notarget = STRIP_DRIVE_SPEC (dir_notarget);
+ /* We will append a slash to debugdir, so remove the leading
+ slash as well. */
+ if (IS_DIR_SEPARATOR (dir_notarget[0]))
+ dir_notarget++;
+ }
+
for (const gdb::unique_xmalloc_ptr<char> &debugdir : debugdir_vec)
{
debugfile = target_prefix ? "target:" : "";
OK to commit to both branches (with the necessary ChangeLog entries)?
Btw, the removal of the leading slash of dir_notarget could
potentially benefit Posix systems as well. Or maybe we should not
append the literal slash in this snippet from
find_separate_debug_file:
debugfile = target_prefix ? "target:" : "";
debugfile += debugdir.get ();
debugfile += "/"; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
debugfile += dir_notarget;
debugfile += debuglink;
since AFAICT dir_notarget will always begin with a slash (I added a
test for that because I wasn't sure that is indeed so).
next reply other threads:[~2019-04-18 13:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 13:49 Eli Zaretskii [this message]
2019-04-18 16:19 ` LRN
2019-04-18 18:41 ` Eli Zaretskii
2019-04-18 21:42 ` LRN
2019-04-19 6:48 ` Eli Zaretskii
2019-04-19 10:06 ` LRN
2019-04-21 12:06 ` Eli Zaretskii
2019-04-21 12:55 ` Simon Marchi
2019-04-22 9:19 ` Eli Zaretskii
2019-04-27 10:56 ` Eli Zaretskii
2019-04-27 16:16 ` Simon Marchi
2019-04-27 16:39 ` Eli Zaretskii
2019-04-27 18:56 ` Simon Marchi
2019-04-27 19:05 ` Eli Zaretskii
2019-05-03 7:36 ` Eli Zaretskii
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=83ef5ze84y.fsf@gnu.org \
--to=eliz@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).