unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: gud-chdir-before-run
Date: Wed, 03 Mar 2010 18:01:46 +0100	[thread overview]
Message-ID: <m3tysxxrt1.fsf@hase.home> (raw)
In-Reply-To: <7rzl2pbt2w.fsf@fencepost.gnu.org> (Eli Zaretskii's message of "Wed, 03 Mar 2010 05:25:11 -0500")

Eli Zaretskii <eliz@gnu.org> writes:

> Why is this option's default value non-nil?  It does the wrong thing
> when the executable is not in the same directory as the sources, because
> the .gdbinit file is usually found where the sources live, so changing
> the directory starts GDB in the wrong place, and .gdbinit is not read.

Usually the .gdbinit lives where the program is built.

> In my usage, I normally type "M-x gdb" from a buffer that visits some
> source file which is compiled into the program I'm about to debug, or
> one of its Makefile's or other scripts.  For this use-case, the current
> default is always wrong.

Without gud-chdir-before-run you need to M-x cd to the build directory
*before* invoking M-x gdb, which would clobber default-directory for the
current buffer.

Alternatively there should be an easy way to do M-x in a different
default-directory then the one from the current buffer.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."




  parent reply	other threads:[~2010-03-03 17:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 10:25 gud-chdir-before-run Eli Zaretskii
2010-03-03 15:23 ` gud-chdir-before-run Stefan Monnier
2010-03-03 17:01 ` Andreas Schwab [this message]
2010-03-03 17:27   ` gud-chdir-before-run Eli Zaretskii
2010-03-03 17:45     ` gud-chdir-before-run Andreas Schwab

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=m3tysxxrt1.fsf@hase.home \
    --to=schwab@linux-m68k.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).