From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alexis Newsgroups: gmane.emacs.help Subject: Re: Random bus error Date: Sat, 10 Jan 2015 17:10:42 +1100 Message-ID: <877fwvqi71.fsf@gmail.com> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1420870465 23462 80.91.229.3 (10 Jan 2015 06:14:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 10 Jan 2015 06:14:25 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jan 10 07:14:19 2015 Return-path: Envelope-to: geh-help-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 1Y9pGd-00066S-W1 for geh-help-gnu-emacs@m.gmane.org; Sat, 10 Jan 2015 07:11:24 +0100 Original-Received: from localhost ([::1]:53236 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y9pGc-0007IE-RU for geh-help-gnu-emacs@m.gmane.org; Sat, 10 Jan 2015 01:11:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y9pG9-0007Ga-Th for help-gnu-emacs@gnu.org; Sat, 10 Jan 2015 01:11:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y9pG6-0002lW-PJ for help-gnu-emacs@gnu.org; Sat, 10 Jan 2015 01:10:53 -0500 Original-Received: from mail-pd0-x22e.google.com ([2607:f8b0:400e:c02::22e]:35412) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y9pG6-0002lS-Hg for help-gnu-emacs@gnu.org; Sat, 10 Jan 2015 01:10:50 -0500 Original-Received: by mail-pd0-f174.google.com with SMTP id fp1so21238595pdb.5 for ; Fri, 09 Jan 2015 22:10:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:to:subject:in-reply-to:date:message-id:mime-version :content-type; bh=8YfkvSaf8T4wuwlxrU4644e/SNCrvbd86+KD83DL5mU=; b=faY2bhcKDt7bF3iyEgO1yhRm3J/BD0IHZWq85l5iSrnUn3L3ankr5GVmBICSJS4w6t 8Ld03r+C/ycoTacFEd5iOeuFU1Yw2jRJ5S5xvXGQPOfdskrHiyYzhhWC4FhouPl6VaTi mFSKb6oj3cYz0tAcNLS7Na/XO6b/86+TA0Hnzrnz+ZZK6WymZsA5jphwLjrIcGV6T33h m/2cweDDnBYTCyREiLgFZGNC7c1w3FNBUjNshD+mFIU2yq951jlGGIP4cwbXiUC0mjdF h/UC9aQdQsKMVCNTmFEwSJ/RD0ppyTTAjoj9pJ8stklT5Z8qPA3dHhISEC446JLHjRq/ KSDA== X-Received: by 10.70.137.42 with SMTP id qf10mr28893873pdb.11.1420870248914; Fri, 09 Jan 2015 22:10:48 -0800 (PST) Original-Received: from localhost (ppp118-209-63-224.lns20.mel4.internode.on.net. [118.209.63.224]) by mx.google.com with ESMTPSA id rr9sm8608236pbc.39.2015.01.09.22.10.46 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 09 Jan 2015 22:10:47 -0800 (PST) In-reply-to: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c02::22e X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 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-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:101988 Archived-At: blacknwhite77@gmail.com writes: > 2. I have very little knowledge of emacs debugger. Is there > documentation somewhere on how to run emacs under a debugger? See the file etc/DEBUG. > Also, as I mentioned earlier, this crash is very random and nothing in > specific triggers it, so I am not sure how running under a debugger > might help. Running Emacs under e.g. gdb can allow one to query for information about the call stack, values of various variables etc. immediately after the crash has happened, and before such information is irretrievably lost. > 3. This seems to be the closest to what might help. I did set the > debug-on-error value in my .emacs, but my question is once the app > crashes where do I find the crash log? `debug-on-error` is more for debugging Emacs Lisp, presenting debugging-related information in a new buffer whilst Emacs is still running. App crashes are probably more likely to be occurring at the C level, hence the need to run Emacs under a C debugger such as gdb - as distinct from using the ELisp debugging facilities built-in to Emacs (e.g. EDebug), which one uses from within Emacs itself. Alexis.