unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Guy Offer <guyof@checkpoint.com>
Cc: 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 13:02:52 +0200	[thread overview]
Message-ID: <83lf1lybdv.fsf@gnu.org> (raw)
In-Reply-To: <45a58bbbf003472e9332306dd261238a@checkpoint.com> (message from Guy Offer on Thu, 18 Nov 2021 08:54:22 +0000)

> From: Guy Offer <guyof@checkpoint.com>
> CC: "kbrown@cornell.edu" <kbrown@cornell.edu>,
>         "51894@debbugs.gnu.org"
> 	<51894@debbugs.gnu.org>
> Date: Thu, 18 Nov 2021 08:54:22 +0000
> 
> Also, can you try "M-x gud-gdb RET" instead, and see if the problem exists there as well?  Maybe there's something in gdb-mi.el that doesn't work well in this case, in particular when it parses the file names reported by GDB's MI interface.  For that reason, I'd be interested to see the raw data about source file names emitted by GDB in response to Emacs's queries.  For that purpose, activate the gdb-enable-debug minor mode, and show the contents of the variable gdb-debug-log after a command that results in such failures.
> 
> =====> The gud-gdb does not have the IDE support (it only runs the gdb on a single window without opening the source files, stack or variable windows).

That's not entirely true: it does open a window with the source file.

Anyway I'm not saying you should use "M-x gud-gdb" instead of "M-x
gdb", I'm asking you to try gud-gdb just this once to see if it is
capable of resolving these file names.  Could you please try that and
report the results?  Knowing that could give some hint about where to
look for the reasons of your original problem.

Thanks.





  reply	other threads:[~2021-11-18 11:02 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 [this message]
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=83lf1lybdv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51894@debbugs.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).