From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: The emacs_backtrace "feature" Date: Sun, 23 Sep 2012 22:05:10 +0900 Message-ID: <87r4psopo9.fsf@uwakimon.sk.tsukuba.ac.jp> References: <83lig3yaci.fsf@gnu.org> <505CC1FA.4070300@cs.ucla.edu> <83fw6akz67.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1348405530 5656 80.91.229.3 (23 Sep 2012 13:05:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 23 Sep 2012 13:05:30 +0000 (UTC) Cc: Paul Eggert , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 23 15:05:35 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TFlsL-0002xI-Oj for ged-emacs-devel@m.gmane.org; Sun, 23 Sep 2012 15:05:33 +0200 Original-Received: from localhost ([::1]:51275 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TFlsG-0006zP-WE for ged-emacs-devel@m.gmane.org; Sun, 23 Sep 2012 09:05:29 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:42235) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TFlsF-0006xG-2i for emacs-devel@gnu.org; Sun, 23 Sep 2012 09:05:27 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TFlsE-00058z-AA for emacs-devel@gnu.org; Sun, 23 Sep 2012 09:05:27 -0400 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:46052) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TFlsC-0004oo-TL; Sun, 23 Sep 2012 09:05:25 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id 1D7539708B4; Sun, 23 Sep 2012 22:05:11 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id D3D201A2AA2; Sun, 23 Sep 2012 22:05:10 +0900 (JST) In-Reply-To: <83fw6akz67.fsf@gnu.org> X-Mailer: VM 8.0.12-devo-585 under 21.5 (beta32) "habanero" b0d40183ac79 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 130.158.97.224 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:153485 Archived-At: 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. :-)