From: Klaus Zeitler <kzeitler@lucent.com>
Cc: emacs-devel@gnu.org
Subject: Re: gdb call with core
Date: Fri, 12 May 2006 14:03:07 +0200 [thread overview]
Message-ID: <q5g64kbjvr8.fsf@sfsw51.de.lucent.com> (raw)
In-Reply-To: <17509.46549.5651.16043@localhost.localdomain> (nickrob@snap.net.nz's message of "Sat, 13 May 2006 22:32:52 +1200")
>>>>> "nickrob" == nickrob <nickrob@snap.net.nz> writes:
nickrob>
nickrob> This is because Emacs sets the working directory to
nickrob> <path-to-emacs> first so that you debug in the directory of the
nickrob> executable. If the Emacs you want to debug is in your path and
nickrob> you know that core is in `default-directory', you can do "gdb
nickrob> emacs core".
yes, that's how I normally work, with the image being in my path.
Since I still have emacs 21.3 first in my PATH, I had to specify the
image with its dir and to my amazement emacs didn't find the core even
though the default dir was the one with the core.
nickrob> Otherwise you have to specify <path-to-core-dir> as
nickrob> you say.
No big deal as you say, but it's one of the rare cases where it's more
convenient in the shell than in emacs. That's why I brought it up.
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: kzeitler@lucent.com |
------------------------------------------
---
Xerox never comes up with anything original.
prev parent reply other threads:[~2006-05-12 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 9:57 gdb call with core Klaus Zeitler
2006-05-12 11:25 ` Eli Zaretskii
2006-05-12 11:50 ` Klaus Zeitler
2006-05-12 13:36 ` Eli Zaretskii
2006-05-12 14:26 ` Stefan Monnier
2006-05-13 6:59 ` Nick Roberts
2006-05-13 16:25 ` Stefan Monnier
2006-05-13 21:45 ` Nick Roberts
2006-05-15 6:14 ` Klaus Zeitler
2006-05-15 20:37 ` Eli Zaretskii
[not found] ` <17509.46549.5651.16043@localhost.localdomain>
2006-05-12 12:03 ` Klaus Zeitler [this message]
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=q5g64kbjvr8.fsf@sfsw51.de.lucent.com \
--to=kzeitler@lucent.com \
--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).