From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.bugs Subject: bug#22058: 25.1.50; emacs_backtrace.txt Date: Mon, 30 Nov 2015 13:11:07 -0600 Message-ID: References: <929593b8-ad63-4b4a-9587-1eef6e821cc6@default> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1448910747 15294 80.91.229.3 (30 Nov 2015 19:12:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Nov 2015 19:12:27 +0000 (UTC) Cc: 22058@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Nov 30 20:12:15 2015 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 1a3Try-0006Z6-TF for geb-bug-gnu-emacs@m.gmane.org; Mon, 30 Nov 2015 20:12:15 +0100 Original-Received: from localhost ([::1]:42867 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3Try-0004Pe-7D for geb-bug-gnu-emacs@m.gmane.org; Mon, 30 Nov 2015 14:12:14 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35388) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3Trq-0004LN-7m for bug-gnu-emacs@gnu.org; Mon, 30 Nov 2015 14:12:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a3Trm-00045S-VE for bug-gnu-emacs@gnu.org; Mon, 30 Nov 2015 14:12:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:43508) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3Trm-00045A-RF for bug-gnu-emacs@gnu.org; Mon, 30 Nov 2015 14:12:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1a3Trm-0002Jn-CW for bug-gnu-emacs@gnu.org; Mon, 30 Nov 2015 14:12:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: John Wiegley Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 30 Nov 2015 19:12:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22058 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo wontfix Original-Received: via spool by 22058-submit@debbugs.gnu.org id=B22058.14489106938875 (code B ref 22058); Mon, 30 Nov 2015 19:12:02 +0000 Original-Received: (at 22058) by debbugs.gnu.org; 30 Nov 2015 19:11:33 +0000 Original-Received: from localhost ([127.0.0.1]:33216 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1a3TrI-0002J4-J8 for submit@debbugs.gnu.org; Mon, 30 Nov 2015 14:11:33 -0500 Original-Received: from mail-qk0-f172.google.com ([209.85.220.172]:33433) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1a3Tqx-0002Id-TW for 22058@debbugs.gnu.org; Mon, 30 Nov 2015 14:11:30 -0500 Original-Received: by qkas77 with SMTP id s77so63478144qka.0 for <22058@debbugs.gnu.org>; Mon, 30 Nov 2015 11:11:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:in-reply-to:date:message-id:references :user-agent:mime-version:content-type; bh=vihgss151eSMAVOuKGy1Q43Q3FrpS7Vpj2fxIifAWJ0=; b=ZBSrv34SKaMkb5F5Tg+HS/Foq2sOhyaTrTkXMcQ5F3CPShlJoo8pjL0YrmRyGWyAqB N/KYffJYs0+Y7FjJWjJQKrmC2PhArumq4OvCFNNrsWQDgXUR6fnefLOrSlToe9lRyRte 5SgKut25ePmq4He2g8OH+Xq9Xli07rWvJ/r8uv7yg+SjZTmC2zxWRTx5nVNWXWjnDHvP jliljYaDcgzcQw9CSi20gNTXtXB5VKEIZ4sFqflPQXsXmOCyp1n4T4Tb9vUEpibKJ5XQ /jkxAjaZqk4kJPOf0KriDN9xN1cglw4nVSeRetohxnPCcnluEMA8JK4ubWNtrR73mJci 3g/Q== X-Received: by 10.55.76.213 with SMTP id z204mr75236038qka.58.1448910671517; Mon, 30 Nov 2015 11:11:11 -0800 (PST) Original-Received: from Hermes-2.local (mail.johnwiegley.com. [208.82.103.192]) by smtp.gmail.com with ESMTPSA id w75sm15483232qka.25.2015.11.30.11.11.10 (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 30 Nov 2015 11:11:10 -0800 (PST) X-Google-Original-From: "John Wiegley" Original-Received: by Hermes-2.local (Postfix, from userid 501) id 315E14A60585; Mon, 30 Nov 2015 13:11:10 -0600 (CST) In-Reply-To: <929593b8-ad63-4b4a-9587-1eef6e821cc6@default> (Drew Adams's message of "Mon, 30 Nov 2015 07:10:19 -0800 (PST)") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 208.118.235.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:109470 Archived-At: >>>>> Drew Adams writes: >> Such a stack trace offers nothing actionable. > Is there a simple way for me to recognize that, from the backtrace? I don't > send bug reports for the fun of it, and I try not to send duplicate > backtrace reports. Apologies for my curt response. In general, a stack trace usually offers us 0-3 pieces of information: 1. The address where each call instruction occurred in the assembly code. (This information is lost if one compiles with -fomit-frame-pointer.) 2. The name of the function associated with that address. (This information is lost when the executable is stripped, which typically happens when installing an optimized build.) 3. The source file and line number associated with that address. (This information is gained when building with debugging enabled.) When you see just "a list of numbers", it means the executable was stripped of all debug and symbol information. This makes it hard to know which functions -- or even libraries -- might be involved in the stack trace. > Many of the backtraces I've submitted have led to immediate or later fixes, > so clearly there is actionable information in some of them. I there a way > for me to know ahead of time, and so not to bother you with reports that > clearly (apparently it's clear to you ;-)) contain no useful info. You can certainly keep sending them; sometimes we can tell from the "shape" of the trace what the problem might be, if we also know what you were doing at the time it happened. > This crash, like all of those I've been reporting for a while now, comes at > a seemingly random time. I see no association with any action I perform or > any particular setting I use. For a while I thought that I could reduce the > number of crashes by turning off icomplete-mode, but now I don't think that > makes a difference. Does it mainly happening while you are typing? Is Emacs busy at that moment? Do you notice any kind of "stall" or lag before the crash occurs? John