From: Guy Offer via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ken Brown <kbrown@cornell.edu>, Eli Zaretskii <eliz@gnu.org>
Cc: "51894@debbugs.gnu.org" <51894@debbugs.gnu.org>
Subject: bug#51894: 27.2; GDB Gud support on Cygwin has trouble accessing shared files on Windows network drives.
Date: Thu, 18 Nov 2021 07:53:37 +0000 [thread overview]
Message-ID: <7bed7b9225494404b83915071b37ea6e@checkpoint.com> (raw)
In-Reply-To: <9fac329f-43d2-a27e-3fd5-f6522993a30f@cornell.edu>
Hi,
Steps to set up this configuration:
Background:
When working on gdb from Emacs you can see the source code from 2 Emacs windows/buffers:
- the gdb command window: the gdb prompt that displays the current source code line.
- the primary source window: an Emacs window that automatically opened and displays the source file with an arrow pointing on the current line being processed.
The problem is that when the source code is on network drive mounted through Windows 10 drives (F:, G:, etc.) it will not be available to one of these windows.
Working machine : Windows 10
* Have the source pointed by a network drive (e.g. F:/source, etc.).
* Install Cygwin on the local machine: (including make, X11, GNU Emacs 27.2, gcc, packages etc.).
* Download and compile gdb 11.1 (I had to compile myself to work with linux target and build x86_64-redhat-linux-gnu-gdb).
* Activate gdb from emacs by : Alt-x, gdb, gdb -i=mi etc.
Now you see the problems:
* If you set the code path (set substitute-path) to the actual code location /cygdrive/f/source the code will be available to the gdb command window but will not be opened automatically in the primary source window/buffer.
* If you set the code location to //cygdrive/f/source the code will be available to the source window - but not to the gdb command window.
Possible solution - mounting the source code through Cygwin /mnt.
Another problem : when the source is not available the Emacs command prompt get into a loop.
Thanks,
Guy
-----Original Message-----
From: Ken Brown [mailto:kbrown@cornell.edu]
Sent: Wednesday, 17 November 2021 19:41
To: Eli Zaretskii <eliz@gnu.org>; Guy Offer <guyof@checkpoint.com>
Cc: 51894@debbugs.gnu.org
Subject: Re: bug#51894: 27.2; GDB Gud support on Cygwin has trouble accessing shared files on Windows network drives.
On 11/17/2021 12:03 PM, Eli Zaretskii wrote:
>> From: Guy Offer <guyof@checkpoint.com>
>> CC: "51894@debbugs.gnu.org" <51894@debbugs.gnu.org>
>> Date: Wed, 17 Nov 2021 15:01:09 +0000 Pls note that this happens only
>> if f is a network drive .
>
> So maybe it's a Cygwin-specific problem with networked drives? I'll
> CC Ken Brown, who is our Cygwin specialist. Ken, does this ring a
> bell? does /cygdrive/x/ fail when X is a networked drive?
I'm not aware of any such problem. I never use networked drives myself, but if Guy can tell me exactly how he created his, I'll see if I can reproduce the problem.
Ken
Secured by Check Point
________________________________
Report suspicious email
<https://mta-cnf.iaas.checkpoint.com/cmta_feedback_request?id=YmQwMzY5YWNmYTQxMTk1MjBlM2NhOThmYTdjN2ZjNWRiMmQ0OGU3ZWIwNGVhOTlmNGM3Zjk1YTFmYjJhZWNiNQ==&t=YWI5ZjBkMjktYmI3Yy00OGI2LWIzYTMtODA0NTRmY2NjODNm>
________________________________
next prev parent reply other threads:[~2021-11-18 7:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 9:22 bug#51894: 27.2; GDB Gud support on Cygwin has trouble accessing shared files on Windows network drives Guy Offer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-16 15:16 ` Eli Zaretskii
2021-11-17 14:00 ` Guy Offer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-17 14:27 ` Eli Zaretskii
2021-11-17 15:01 ` Guy Offer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-17 17:03 ` Eli Zaretskii
2021-11-17 17:40 ` Ken Brown
2021-11-18 7:53 ` Guy Offer via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-11-18 8:40 ` Eli Zaretskii
2021-11-18 8:54 ` Guy Offer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-18 11:02 ` Eli Zaretskii
2021-11-18 14:17 ` Ken Brown
2021-11-18 14:58 ` Eli Zaretskii
2021-11-18 20:15 ` Ken Brown
2021-12-23 10:22 ` Lars Ingebrigtsen
2021-12-23 13:45 ` Ken Brown
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7bed7b9225494404b83915071b37ea6e@checkpoint.com \
--to=bug-gnu-emacs@gnu.org \
--cc=51894@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=guyof@checkpoint.com \
--cc=kbrown@cornell.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).