From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: guyof@checkpoint.com, 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 15:15:41 -0500 [thread overview]
Message-ID: <7c139527-7783-40ae-ece1-4bc61f1dfacc@cornell.edu> (raw)
In-Reply-To: <835yspy0gq.fsf@gnu.org>
On 11/18/2021 9:58 AM, Eli Zaretskii wrote:
> Thanks. So some other factor must be at work here. I think the
> solution of the riddle is somewhere in what GDB/MI returns to Emacs in
> response to its requests, which is why I asked for gdb-debug-log
> contents.
One other thing that could be relevant is that Guy is using a self-built gdb
11.1, based presumably on the upstream sources. Cygwin's gdb is at version
10.2, and the maintainer has applied 9 patches to the upstream sources.
Guy, maybe you should try imitating the build of Cygwin's gdb-10.2 package.
Ken
next prev parent reply other threads:[~2021-11-18 20:15 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
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 [this message]
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=7c139527-7783-40ae-ece1-4bc61f1dfacc@cornell.edu \
--to=kbrown@cornell.edu \
--cc=51894@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=guyof@checkpoint.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.
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).