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

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: rms <at> gnu.org
Cc: stefankangas <at> gmail.com, 58826 <at> debbugs.gnu.org, dima <at> secretsauce.net
Subject: Re: bug#58826: 29.0.50;
 gud-gdb can't find core file if executable is in a different directory
Date: Sun, 20 Nov 2022 09:45:02 +0200

> From: Richard Stallman <rms <at> gnu.org>
> Cc: stefankangas <at> gmail.com, 58826 <at> debbugs.gnu.org,
> 	dima <at> secretsauce.net
> Date: Sat, 19 Nov 2022 20:15:40 -0500
> 
>   > The above means that the default-directory of the *gud-FILE* buffer
>   > will be different depending on whether at gud-gdb's prompt you type
>   > the GDB command with the program to debug in its absolute file-name
>   > form:
> 
>   >    gdb ... /foo/bar/baz ...
> 
>   > or you type
> 
>   >    gdb ... baz ...
> 
>   > and let GDB find 'baz' by searching PATH.
> 
> Indeed, that can happen.
> 
> But does GDB have a command to specify the file name of the core dump?

Yes, it does.

> If it does, can you override that mistaken heuristic choice by specifying
> the complete file name of the core dump?

No, because the default-directory of the *gud-FILE* buffer is already set by
the time you get the GDB prompt.

You can, of course, "M-x cd" in the buffer.

Previous Next

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