GNU bug report logs - #58826
29.0.50; gud-gdb can't find core file if executable is in a different directory

Previous Next

Full log

Message #47 received at 58826 <at> debbugs.gnu.org (full text, mbox):

From: Richard Stallman <rms <at> gnu.org>
To: Dima Kogan <dima <at> secretsauce.net>
Cc: eliz <at> gnu.org, stefankangas <at> gmail.com, 58826 <at> debbugs.gnu.org
Subject: Re: 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

[[[ 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)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.