GNU bug report logs - #58826
29.0.50; gud-gdb can't find core file if executable is in a different directory

Previous Next

Full log

View this message in rfc822 format

From: Dima Kogan <dima <at> secretsauce.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 58826 <at> debbugs.gnu.org
Subject: bug#58826: 29.0.50; gud-gdb can't find core file if executable is in a different directory
Date: Thu, 27 Oct 2022 23:29:37 -0700

Thanks for replying, Eli.


Eli Zaretskii <eliz <at> gnu.org> writes:

> This is the documented behavior of "M-x gud-gdb":
> .....
> AFAIU, if you run the debugger like this:
>
>   gdb --fullname python3 core.sfmviz.py.1807941
>
> then GUD will not change the default-directory to /usr/bin, which I
> believe is what you want.  GDB will then locate the Python executable
> either in the current default-directory or by searching PATH.

OK. It's documented, but it's still not good. What if the executable
wasn't in the $PATH?

It's also really unintuitive to have an implicit change of directory
here, and it would match most people's expectations if it was changed, I
think. Do you know why we're doing that?

Thanks.

Previous Next

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