all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Enhancement to report-emacs-bug
Date: Thu, 21 Jul 2005 14:08:45 +0200	[thread overview]
Message-ID: <m3d5pc4b02.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <dbm1pg$g4r$1@sea.gmane.org> (Kevin Rodgers's message of "Wed, 20 Jul 2005 11:31:25 -0600")

Kevin Rodgers <ihs_4664@yahoo.com> writes:

> Note that you can provide a full path to the etc/DEBUG file:
> (expand-file-name "etc/DEBUG" data-directory)

Thanks, I did that in the change I installed.

> But how about providing an Emacs command to debug the crash and
> instructions on how to use it:

This is a very good suggestion -- but I think it needs a little more
work to handle cases where people already run emacs in gdb, etc.

You are welcome to work on that.

>
> 	If emacs crashed, try running the gdb debugger on the program
> 	and its core file:
> 	
> 		M-x gdb-emacs-crash
> 		(gdb) bt full
> 		(gdb) xbacktrace
> 	
> 	Then insert the *gud* buffer into this report.  The file
> 	/usr/local/share/emacs/21.3/etc/DEBUG explains how to further
> 	debug the crash.
>
> (defun gdb-emacs-crash (program core)
>    "*Run gdb on the crashed emacs PROGRAM and its dumped CORE file."
>    (interactive
>     (let ((insert-default-directory t))
>       (list (read-file-name "Program: "
>                             invocation-directory nil t invocation-name)
>             (read-file-name "Core: "
>                             (with-current-buffer "*scratch*"
>                               default-directory)
>                             nil
>                             t
>                             "core"))))
>    (gdb (format "gdb %s %s" program core)))

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2005-07-21 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 15:03 Enhancement to report-emacs-bug Kim F. Storm
2005-07-20 17:31 ` Kevin Rodgers
2005-07-21 12:08   ` Kim F. Storm [this message]
2005-07-21 16:22     ` Kevin Rodgers
2005-07-21  3:58 ` Richard M. Stallman

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=m3d5pc4b02.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --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 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.