From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefankangas@gmail.com, 58826@debbugs.gnu.org, dima@secretsauce.net
Subject: bug#58826: 29.0.50; gud-gdb can't find core file if executable is in a different directory
Date: Wed, 23 Nov 2022 18:16:27 -0500 [thread overview]
Message-ID: <E1oxyyh-0003h7-K0@fencepost.gnu.org> (raw)
In-Reply-To: <83wn7q5atd.fsf@gnu.org> (message from Eli Zaretskii on Sun, 20 Nov 2022 09:45:02 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> 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.
Could we fix this by adding a new option to GDB to specify the working
directory? The gud.el could use that option
if it sees that GDB's default choice for working directory
would not be correct.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-11-23 23:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 23:52 bug#58826: 29.0.50; gud-gdb can't find core file if executable is in a different directory Dima Kogan
2022-10-28 6:23 ` Eli Zaretskii
2022-10-28 6:29 ` Dima Kogan
2022-10-28 7:20 ` Eli Zaretskii
2022-11-13 4:32 ` Stefan Kangas
2022-11-15 4:17 ` Richard Stallman
2022-11-15 13:46 ` Eli Zaretskii
2022-11-18 5:05 ` Richard Stallman
2022-11-18 8:23 ` Eli Zaretskii
2022-11-20 1:15 ` Richard Stallman
2022-11-20 7:45 ` Eli Zaretskii
2022-11-23 23:16 ` Richard Stallman [this message]
2022-11-23 23:17 ` Dima Kogan
2022-11-26 0:50 ` Richard Stallman
2022-11-24 6:55 ` Eli Zaretskii
2022-12-29 3:14 ` Richard Stallman
2022-12-29 6:19 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1oxyyh-0003h7-K0@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=58826@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--cc=eliz@gnu.org \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).