all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: The emacs_backtrace "feature"
Date: Sun, 23 Sep 2012 22:05:10 +0900	[thread overview]
Message-ID: <87r4psopo9.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <83fw6akz67.fsf@gnu.org>

Eli Zaretskii writes:

 > It strikes me that we should tell the users how to enable core files,
 > in the same section of the manual.

It strikes me that you could add it to the crash report, since you're
intercepting fatal errors anyway.

Something like:

On Unix-like systems, you can enable core files with "ulimit -c unlimited."

This is useful because the first useful thing the user is going to do
(assuming emacs isn't totally bollixed) is to fire up another emacs to
make the bug report.  May as well have core files enabled for that
instance, too. :-)



  parent reply	other threads:[~2012-09-23 13:05 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  9:49 The emacs_backtrace "feature" Eli Zaretskii
2012-09-21  9:58 ` Andreas Schwab
2012-09-21 10:17   ` Eli Zaretskii
2012-09-21 12:00     ` Andreas Schwab
2012-09-21 19:29   ` Florian Weimer
2012-09-21 19:45     ` Paul Eggert
2012-09-24 15:52       ` Steinar Bang
2012-09-21 12:24 ` Óscar Fuentes
2012-09-21 16:35   ` Stefan Monnier
2012-09-21 16:49 ` Stephen J. Turnbull
2012-09-21 17:07   ` Tom Tromey
2012-09-21 17:41   ` Andreas Schwab
2012-09-21 19:37 ` Paul Eggert
2012-09-22 12:05   ` Richard Stallman
2012-09-22 13:54     ` Christoph Scholtes
2012-09-22 14:23       ` covici
2012-09-24 15:55     ` Steinar Bang
2012-09-24 17:29       ` Paul Eggert
2012-09-22 12:41   ` Eli Zaretskii
2012-09-22 19:28     ` Paul Eggert
2012-09-23 13:05     ` Stephen J. Turnbull [this message]
2012-09-23 14:19       ` Andreas Schwab
2012-09-23 19:30         ` Stephen J. Turnbull
2012-09-23 21:01           ` Nix
2012-09-24  5:00             ` Stephen J. Turnbull
2012-09-24  9:29               ` Nix
2012-09-24 23:55                 ` Stephen J. Turnbull
2012-09-29 19:31   ` Juri Linkov
2012-09-29 20:01     ` Eli Zaretskii
2012-09-29 20:51       ` Paul Eggert
2012-09-29 21:19         ` Eli Zaretskii
2012-09-30  1:30           ` Paul Eggert
2012-09-30  9:44             ` messages-buffer-max-lines (was: The emacs_backtrace "feature") Juri Linkov
2012-10-01  5:51               ` messages-buffer-max-lines Paul Eggert
2012-10-01  6:50                 ` messages-buffer-max-lines Chong Yidong
2012-09-30  1:48       ` The emacs_backtrace "feature" Stefan Monnier
2012-09-30  7:14         ` Eli Zaretskii
2012-09-30  7:24           ` Paul Eggert
2012-10-01  2:54         ` Chong Yidong
2012-10-01 11:43           ` Lars Magne Ingebrigtsen
2012-09-21 21:40 ` Richard Stallman
2012-09-22  6:53   ` Stephen J. Turnbull
2012-09-24 14:27   ` Lars Ingebrigtsen

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=87r4psopo9.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=eggert@cs.ucla.edu \
    --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 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.