From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.help Subject: Re: Help debugging a backtrace Date: Wed, 21 Sep 2016 17:12:22 +0000 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1474478027 30676 195.159.176.226 (21 Sep 2016 17:13:47 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 21 Sep 2016 17:13:47 +0000 (UTC) To: Jude DaShiell , 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 Wed Sep 21 19:13:39 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 1bml5D-0004hl-5y for geh-help-gnu-emacs@m.gmane.org; Wed, 21 Sep 2016 19:13:19 +0200 Original-Received: from localhost ([::1]:45498 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bml5B-0000uk-DF for geh-help-gnu-emacs@m.gmane.org; Wed, 21 Sep 2016 13:13:17 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43410) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bml4W-0000rT-3o for help-gnu-emacs@gnu.org; Wed, 21 Sep 2016 13:12:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bml4T-0000KI-W7 for help-gnu-emacs@gnu.org; Wed, 21 Sep 2016 13:12:35 -0400 Original-Received: from mail-yw0-x22f.google.com ([2607:f8b0:4002:c05::22f]:34820) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bml4T-0000KC-Rp for help-gnu-emacs@gnu.org; Wed, 21 Sep 2016 13:12:33 -0400 Original-Received: by mail-yw0-x22f.google.com with SMTP id u82so63654595ywc.2 for ; Wed, 21 Sep 2016 10:12:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=M6wPzSh+wsmPmGPv4jITRdb0b7VPJ+xLmG355aHAYRA=; b=xdRC7XGWz6pVjCUlB9dTdjyLO4A5pvbgtczBlgFk+EyTnY/asFbCSE8vk5qaqcKN2K FfLIQkkg/1dDyQcebceTwjP8CVLOo/Y84pqp6bOSbVZbDyBCrv4WSaohPYmDAGkTf6DS dpEqE5YpaqgyRcYMGaQbBYY037d1z4gzBq06fCC30tgLDimXl4nfgCkk9U2l08DCXa9O bX2IBApPPH6ToCsDhZQ09Vn+2O4Lw7XjvCBMhW0fyxdHeFJr2JyUYxFZ7WYy5XOxTVRf C500DK6KxzE4Aw2wBzHu0L92SBmbplQaVaNNldUEYqw0zBe6HGWXHI3yl9m5zTpd3Lgk 0YXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=M6wPzSh+wsmPmGPv4jITRdb0b7VPJ+xLmG355aHAYRA=; b=CPWnbLewzBDonf3wj+vRjaGAZQ4/GuxxZ5PfUzXZDvJa2Teen0QR6qQuRxX6wS4sj9 SXF+TYv3NA3IVpcvNRbjzNxaMeSDIw/RY7BwZC8qXDhSKzN9nqi27CI+vIT8Vu/0ur9y Ms1xezVC9fn+RvfZwUDzNqlnBLM/+TFruRHLRDYOaHFbF1bygYhpr+MMgJNk/sOiQ1b7 0J3B0oYyQqxcwFvzLAFNiHKw4E6mC4qy8v9Av6V0/EjQJZCiuChoJe2s96/pdBCZn3bt ZqnKZSA9P/LZo07t2Xj6H4vgXossMEZ4+3FKp4f0ubqGi4bVqAMuf8wIZ4ANRvo0x0WR 4B9g== X-Gm-Message-State: AE9vXwOfxdEk5DV0CLKTqQwi3XL0b4GYmQpoGN+K2piR2qJ3jhhXXRn1Jq0mTTtLIbLtk1kH75C5+v69giP1uA== X-Received: by 10.13.253.134 with SMTP id n128mr39271549ywf.20.1474477953288; Wed, 21 Sep 2016 10:12:33 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4002:c05::22f X-Content-Filtered-By: Mailman/MimeDel 2.1.21 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:111368 Archived-At: 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). -- Kaushal Modi