From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix lookup of separate debug file on MS-Windows
Date: Sat, 27 Apr 2019 19:05:00 -0000 [thread overview]
Message-ID: <837ebfuv5m.fsf@gnu.org> (raw)
In-Reply-To: <2ef82187bed72c3fbe61d851c2d6781b@simark.ca> (message from Simon Marchi on Sat, 27 Apr 2019 14:56:11 -0400)
> Date: Sat, 27 Apr 2019 14:56:11 -0400
> From: Simon Marchi <simark@simark.ca>
> Cc: gdb-patches@sourceware.org
>
> Given the complexity of supporting all these scenarios (if we want to
> support them, we at least want to test them, which is a lot of work) and
> the fact that they are all theoretical at this point, I would be fine to
> go with what you had in your patch (using HAS_DRIVE_SPEC). If somebody
> ever needs to remotely debug a Windows machine from a Linux machine and
> have GDB find separate debug file in the remote debug file directory...
> then they can add the missing pieces :).
OK, thanks. I will wait for a day or two for any other comments, and
if nothing comes up, will push with a FIXME comment regarding the
remote debugging use cases.
next prev parent reply other threads:[~2019-04-27 19:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 13:49 Eli Zaretskii
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 [this message]
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=837ebfuv5m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.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).