From: Richard Stallman <rms@gnu.org>
To: Dima Kogan <dima@secretsauce.net>
Cc: eliz@gnu.org, stefankangas@gmail.com, 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: Fri, 25 Nov 2022 19:50:12 -0500 [thread overview]
Message-ID: <E1oyjOW-0004MD-Vt@fencepost.gnu.org> (raw)
In-Reply-To: <87tu2pp8au.fsf@secretsauce.net> (message from Dima Kogan on Wed, 23 Nov 2022 15:17:49 -0800)
[[[ 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. ]]]
> > Could we fix this by adding a new option to GDB to specify the working
> > directory?
> This exists: you can "gdb --cd DIR"
I figured there would be one. However, is that what we want in this case?
Do we want GDB to run with a different working directory, or only to
find the core file in that directory?
> But that doesn't matter: this is a gud issue. The complaint was that
> running "gdb ARGS" in a shell sometimes doesn't do the same thing as M-x
> gud "gdb ARGS", even with the same ARGS
The question is, why not fix this with a change in GUD? People were
talking about an obstacle to doing so, but I didn't see a clear
statement of what the obstacle was. It seemed to be about whether GUD
can tell GDB to find the core dump in the right place.
If --cd enables GDB to find the core dump in the right place,
why not make GUD send that argument?
Does that fail to do the job right?
--
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-26 0:50 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1oyjOW-0004MD-Vt@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 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.