From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#13775: 24.3.50; Omissions in documentation for crash reporting Date: Thu, 21 Feb 2013 19:24:03 +0200 Message-ID: <837gm1oa18.fsf@gnu.org> References: <87bobei0tx.fsf@yandex.ru> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1361467500 15883 80.91.229.3 (21 Feb 2013 17:25:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Feb 2013 17:25:00 +0000 (UTC) Cc: 13775@debbugs.gnu.org To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Feb 21 18:25:23 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1U8ZtX-0001ec-K5 for geb-bug-gnu-emacs@m.gmane.org; Thu, 21 Feb 2013 18:25:19 +0100 Original-Received: from localhost ([::1]:36825 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U8ZtC-000872-Tm for geb-bug-gnu-emacs@m.gmane.org; Thu, 21 Feb 2013 12:24:58 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:41247) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U8Zt5-0007vY-Rj for bug-gnu-emacs@gnu.org; Thu, 21 Feb 2013 12:24:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U8Zsz-0003qs-8k for bug-gnu-emacs@gnu.org; Thu, 21 Feb 2013 12:24:51 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:37258) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U8Zsz-0003qG-5b for bug-gnu-emacs@gnu.org; Thu, 21 Feb 2013 12:24:45 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1U8ZuE-00075a-3m for bug-gnu-emacs@gnu.org; Thu, 21 Feb 2013 12:26:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 21 Feb 2013 17:26:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13775 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 13775-submit@debbugs.gnu.org id=B13775.136146751027187 (code B ref 13775); Thu, 21 Feb 2013 17:26:02 +0000 Original-Received: (at 13775) by debbugs.gnu.org; 21 Feb 2013 17:25:10 +0000 Original-Received: from localhost ([127.0.0.1]:42722 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1U8ZtO-00074S-BR for submit@debbugs.gnu.org; Thu, 21 Feb 2013 12:25:10 -0500 Original-Received: from mtaout21.012.net.il ([80.179.55.169]:35532) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1U8ZtK-00074I-4Q for 13775@debbugs.gnu.org; Thu, 21 Feb 2013 12:25:09 -0500 Original-Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0MIK00K00YX0MJ00@a-mtaout21.012.net.il> for 13775@debbugs.gnu.org; Thu, 21 Feb 2013 19:23:47 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MIK00K8EYZMMF10@a-mtaout21.012.net.il>; Thu, 21 Feb 2013 19:23:47 +0200 (IST) In-reply-to: <87bobei0tx.fsf@yandex.ru> X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:71600 Archived-At: > From: Dmitry Gutov > Date: Thu, 21 Feb 2013 11:27:06 +0400 > > As a non-GDB-wielding user with not much C experience, I had a hard time > following the instructions in `report-emacs-bug' and the ones that > followed. I'm not sure your expectations can be met with any reasonable effort. There's no way we can teach everybody the basics of GNU-style configure scripts, including how to discover the available switches and override compiler and linker options. You need to learn that elsewhere. In general, if you cannot figure out how to do something, just ask, and you _will_ be helped. Some answers below, because most of this info is available, you just need to know how to find it. > 1. Calling `xbacktrace' requires src/.gdbinit to be loaded. It > a) requires the user to run gdb exactly from src/ (not `gdb src/emacs'), The file etc/DEBUG tells you that at the beginning: ** When you debug Emacs with GDB, you should start it in the directory where the executable was made. That directory has a .gdbinit file that defines various "user-defined" commands for debugging Emacs. (These commands are described below under "Examining Lisp object values" and "Debugging Emacs Redisplay problems".) > b) requires them to modify the `auto-load safe-path', or that .gdbinit > is ignored. This "feature" entered GDB only recently. Versions of GDB before 7.5 don't need that, and will barf if you use this command. I don't see any reasonable way of dealing with this without confusing newbies even more (while veteran GDB users already know how to negotiate this obstacle). > 2. "Compile without optimizations" - how do I do that? `configure > --help' doesn't seem to show any pertinent options. ...but wait, it says > I can override the choices made by the script. Yes, it says near the end how to specify compiler switches. > a) Do I set the variable when calling `make', or do I have to re-run > ./configure? Not obvious, the answer is "the latter". Actually, both will work. > b) I don't know the choice the script made, how do I not break > anything by overriding it? You just need to know, or ask. It is not reasonable to expect Emacs documentation to repeat the entire compiler manual, or large portions thereof. > 3. In #13749 (which caused me to write this), Paul also suggests using > -DENABLE_CHECKING. If I'm not mistaken, this variable isn't documented > anywhere. As Andreas points out, this is in "./configure --help".