From: Dima Kogan <dima@secretsauce.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58826@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 [thread overview]
Message-ID: <87y1t0mp40.fsf@secretsauce.net> (raw)
In-Reply-To: <83zgdgjwk3.fsf@gnu.org>
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.
next prev parent reply other threads:[~2022-10-28 6:29 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 [this message]
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
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=87y1t0mp40.fsf@secretsauce.net \
--to=dima@secretsauce.net \
--cc=58826@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).