bug#51894: 27.2; GDB Gud support on Cygwin has trouble accessing shared files on Windows network drives.

[Guy Offer]

-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org] 
Sent: Thursday, 18 November 2021 10:41
To: Guy Offer <guyof@checkpoint.com>
Cc: kbrown@cornell.edu; 51894@debbugs.gnu.org
Subject: Re: bug#51894: 27.2; GDB Gud support on Cygwin has trouble accessing 
shared files on Windows network drives.

> From: Guy Offer <guyof@checkpoint.com>
> CC: "51894@debbugs.gnu.org" <51894@debbugs.gnu.org>
> Date: Thu, 18 Nov 2021 07:53:37 +0000
> 
> * 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. 

Why is "set substitute-path" command needed?  The program you are debugging 
should have the source location recorded in the debug info, so that step should 
not be needed.


I'm asking because perhaps this step is an important part of the problem.
===>
        It was compiled on a different location. 
        I had the same problem occurring when using the "directory" command 
(adding a directory to the source search path) as well.


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).

> Another problem : when the source is not available the Emacs command prompt 
> get into a loop.

I believe that was fixed in Emacs 28.


Secured by Check Point


________________________________

Report suspicious email
<https://mta-cnf.iaas.checkpoint.com/cmta_feedback_request?id=OTNmODc4NjYzMTE2NzlhOTZkNmI2NGQ4ZjI2MmY4ZjI2NDhhMDc4OTcyNmZkYjFmYzI0ZjMwNThiZTM5OGMyMA==&t=YWI5ZjBkMjktYmI3Yy00OGI2LWIzYTMtODA0NTRmY2NjODNm>
________________________________