GNU bug report logs - #79036
[PATCH] Fix pdb tracking for remote filenames

Previous Next

Full log

Message #83 received at 79036 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: liuhui1610 <at> gmail.com, kobarity <at> gmail.com, 79036 <at> debbugs.gnu.org
Subject: Re: bug#79036: [PATCH] Fix pdb tracking for remote filenames
Date: Fri, 18 Jul 2025 17:53:55 +0300

> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  kobarity <at> gmail.com,  79036 <at> debbugs.gnu.org
> Date: Fri, 18 Jul 2025 16:13:00 +0200
> 
> Liu Hui <liuhui1610 <at> gmail.com> writes:
> 
> > For example, below is the pdb output in a remote python shell, and the
> > file-name "/tmp/test.py" is local. Because of the "from ... import
> > ...", we can know the file is on the remote system.
> >
> >     >>> from test import f; f()
> >     > /tmp/test.py(3)f()
> >     -> return 1
> >     (Pdb)
> >
> > However, with the following pdb output in a remote python shell
> >
> >     >>> f()
> >     > /tmp/test.py(3)f()
> >     -> return 1
> >     (Pdb)
> >
> > The local filename "/tmp/test.py" may be on the remote system like the
> > above case, or may be on the local host if we press C-c C-c to send
> > its code to the remote process.
> >
> > Which file should python shell track? The simplest solution is to
> > check which file exists.
> 
> No. The mature check is whether default-directory is remote. Everything
> else is voodoo. Can work, but no guarantee.

Right.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.