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

[Dima Kogan]

Thanks for replying, Eli.


Eli Zaretskii <eliz@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.