From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Skipping unexec via a big .elc file Date: Sat, 14 Jan 2017 22:13:42 +0200 Message-ID: <83y3yd9z7t.fsf@gnu.org> References: <3CC6BB36-1794-4202-8243-132E0345B236@raeburn.org> <52BDCC33-546C-4F47-A230-00EBC813B038@raeburn.org> <15CF14CC-C7DE-44BA-AC7D-F0BF1F160979@raeburn.org> <9463F91F-DB82-48E1-BE01-1E2BC8DA0766@raeburn.org> <831swxzbw8.fsf@gnu.org> <83y3z2wphb.fsf@gnu.org> <83tw9bb42m.fsf@gnu.org> <349ED8B9-C34B-495B-9FB5-E72CE6EFCA38@raeburn.org> <87inpni6xa.fsf@linux-m68k.org> <8360lmesso.fsf@gnu.org> <3B044D64-7C94-42D7-BE1B-7A9CA76C5A67@raeburn.org> <83k29xc49v.fsf@gnu.org> <834m11bksl.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1484424865 16479 195.159.176.226 (14 Jan 2017 20:14:25 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 14 Jan 2017 20:14:25 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 14 21:14:19 2017 Return-path: Envelope-to: ged-emacs-devel@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 1cSUiP-0003SH-4x for ged-emacs-devel@m.gmane.org; Sat, 14 Jan 2017 21:14:17 +0100 Original-Received: from localhost ([::1]:49271 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cSUiR-0002I1-UU for ged-emacs-devel@m.gmane.org; Sat, 14 Jan 2017 15:14:19 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58886) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cSUiH-0002GS-5N for emacs-devel@gnu.org; Sat, 14 Jan 2017 15:14:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cSUiE-00049w-0R for emacs-devel@gnu.org; Sat, 14 Jan 2017 15:14:09 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:59641) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cSUiD-00049q-TB; Sat, 14 Jan 2017 15:14:05 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1364 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cSUi9-0005hh-9C; Sat, 14 Jan 2017 15:14:05 -0500 In-reply-to: (message from Stefan Monnier on Sat, 14 Jan 2017 13:11:26 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:211300 Archived-At: > From: Stefan Monnier > Date: Sat, 14 Jan 2017 13:11:26 -0500 > > >> You can set byte-compile-debug (along with debug-on-error) to get > >> a backtrace which will be more useful. > > That doesn't help when one is presented with a build log. > > Not directly, no, indeed. Usually I then fire an interactive Emacs, set > the vars and call byte-compile-file to reproduce the problem in an > environment where I can investigate the backtrace comfortably. There's more than one way of tracking the real locus of the problem. My point is that either way, it's an annoyance which makes investigation of such problems significantly less efficient than when the byte compiler points out the source file and the line number where it happens, or close thereabouts (which is what happens most of the time). I gather that we are in violent agreement about that.