From: Dima Kogan <dima@secretsauce.net>
To: 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 16:52:32 -0700 [thread overview]
Message-ID: <87wn8komdb.fsf@jpl.nasa.gov> (raw)
Hi. I'm using a bleeding-edge build of emacs, although I think this is a
very old bug.
I just ran a Python program in $DIRECTORY:
python3 program.py
python3 is in /usr/bin. There was a bug, the program crashed, dumped
core, and I want to debug it. I do this from the buffer containing
program.py (default-directory is $DIRECTORY, which contains program.py
and is NOT /usr/bin)
M-x gud-gdb
gdb --fullname /usr/bin/python3 core.sfmviz.py.1807941
It says this:
/usr/bin/core.sfmviz.py.1807941: No such file or directory.
It works fine from the shell, outside of emacs. The issue is that
gud-gdb is changing default-directory to /usr/bin (where the binary
executable lives). But I never asked for that, and this is unexpected:
I'd expect it to do the same thing as that gdb command would do in the
shell.
Thanks
next reply other threads:[~2022-10-27 23:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 23:52 Dima Kogan [this message]
2022-10-28 6:23 ` bug#58826: 29.0.50; gud-gdb can't find core file if executable is in a different directory 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
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=87wn8komdb.fsf@jpl.nasa.gov \
--to=dima@secretsauce.net \
--cc=58826@debbugs.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).