From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Jude DaShiell Newsgroups: gmane.emacs.help Subject: Re: Help debugging a backtrace Date: Thu, 22 Sep 2016 14:52:46 -0400 (EDT) Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Trace: blaine.gmane.org 1474573613 8958 195.159.176.226 (22 Sep 2016 19:46:53 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 22 Sep 2016 19:46:53 +0000 (UTC) User-Agent: Alpine 2.20 (NEB 67 2015-01-07) To: Kaushal Modi , rn3aoh.g@gmail.com, help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Sep 22 21:46:49 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bn9xH-0001jL-95 for geh-help-gnu-emacs@m.gmane.org; Thu, 22 Sep 2016 21:46:47 +0200 Original-Received: from localhost ([::1]:59264 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bn9xH-0002zC-VA for geh-help-gnu-emacs@m.gmane.org; Thu, 22 Sep 2016 15:46:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bn97E-0004Vy-Jy for help-gnu-emacs@gnu.org; Thu, 22 Sep 2016 14:53:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bn977-0002jV-28 for help-gnu-emacs@gnu.org; Thu, 22 Sep 2016 14:52:58 -0400 Original-Received: from mailbackend.panix.com ([166.84.1.89]:55200) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bn976-0002fv-Ui for help-gnu-emacs@gnu.org; Thu, 22 Sep 2016 14:52:52 -0400 Original-Received: from panix1.panix.com (panix1.panix.com [166.84.1.1]) by mailbackend.panix.com (Postfix) with ESMTP id 0040D1B91D; Thu, 22 Sep 2016 14:52:46 -0400 (EDT) Original-Received: by panix1.panix.com (Postfix, from userid 20712) id DA2EC14B9A; Thu, 22 Sep 2016 14:52:46 -0400 (EDT) Original-Received: from localhost (localhost [127.0.0.1]) by panix1.panix.com (Postfix) with ESMTP id D654714B98; Thu, 22 Sep 2016 14:52:46 -0400 (EDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux (Android) X-Received-From: 166.84.1.89 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:111375 Archived-At: Thanks much, this is a huge help. I didn't know exactly how to read back traces so ought to be able to fix things more effectively in future. On Wed, 21 Sep 2016, Kaushal Modi wrote: > Date: Wed, 21 Sep 2016 13:12:22 > From: Kaushal Modi > To: Jude DaShiell , rn3aoh.g@gmail.com, > help-gnu-emacs@gnu.org > Subject: Re: Help debugging a backtrace > > On Tue, Sep 20, 2016 at 9:53 PM Jude DaShiell wrote: > >> Is it possible with a debug situation where a .emacs has to be debugged >> to run emacs --debug then key in some command that has emacs tell you >> what the first line is that has the error? >> > > I am not sure what you mean by that. > > When you run emacs --debug-init, it will show you an elisp backtrace of the > first error in your emacs config. If your config has no error, you will see > emacs start as usual. The backtrace will lead to the first line causing > that error. > > Once your emacs session has started, and you want a backtrace on any error > that occurs later on in the session, do M-x toggle-debug-on-error. Then you > will get a backtrace on any error (even the harmless ones). > > > --