From: Eli Zaretskii <eliz@gnu.org>
To: rms@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: Thu, 29 Dec 2022 08:19:58 +0200 [thread overview]
Message-ID: <83o7rm91f5.fsf@gnu.org> (raw)
In-Reply-To: <E1pAjN0-0007q0-OX@fencepost.gnu.org> (message from Richard Stallman on Wed, 28 Dec 2022 22:14:14 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: stefankangas@gmail.com, 58826@debbugs.gnu.org,
> dima@secretsauce.net
> Date: Wed, 28 Dec 2022 22:14:14 -0500
>
> > Telling GDB to chdir to another directory will not affect the
> > default-directory of the *gud-FILE* buffer, and that was the OP's problem:
> > the fact that typing a relative file name was interpreted relative to a
> > directory he didn't expect.
>
> It must be Emacs Lisp code that creates the *gud-FILE* buffer
> and handles these relative file name. Can't that code be changed
> to DTRT?
The argument here, and the original problem, is about what is "TRT".
For some (many) use cases, what the code does now is already TRT. I
attempted to explain that up-thread:
IME, the current behavior covers most of the use cases: either you are
debugging a program you are developing from its source tree, or you
are debugging an installed program that's on 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?
If you think about that, it's actually quite natural: it makes the
files you are likely to access from the debug session appear in the
current directory.
In any case, this is a long-standing behavior.
prev parent reply other threads:[~2022-12-29 6:19 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o7rm91f5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58826@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.