From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Skipping unexec via a big .elc file Date: Sat, 14 Jan 2017 13:11:26 -0500 Message-ID: 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> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1484417553 4873 195.159.176.226 (14 Jan 2017 18:12:33 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 14 Jan 2017 18:12:33 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 14 19:12:29 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 1cSSoV-0000gm-Gk for ged-emacs-devel@m.gmane.org; Sat, 14 Jan 2017 19:12:27 +0100 Original-Received: from localhost ([::1]:48965 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cSSoa-0002Uh-4n for ged-emacs-devel@m.gmane.org; Sat, 14 Jan 2017 13:12:32 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44024) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cSSo2-0002T5-FP for emacs-devel@gnu.org; Sat, 14 Jan 2017 13:11:59 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cSSny-0008Di-Fc for emacs-devel@gnu.org; Sat, 14 Jan 2017 13:11:58 -0500 Original-Received: from [195.159.176.226] (port=41352 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cSSny-0008DR-7u for emacs-devel@gnu.org; Sat, 14 Jan 2017 13:11:54 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cSSne-0004aK-53 for emacs-devel@gnu.org; Sat, 14 Jan 2017 19:11:34 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 17 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:CUIyzYvLEJHW3hKoq+Sv2eO1ytA= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 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:211293 Archived-At: >> 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. My point was simply that this is an *evaluation* error more than an error in the compiled code, so the poverty of the info is due to the poverty of info we get when running Elisp code (and this is indeed somewhat linked to the byte-compiler since the byte-compiler doesn't preserve the source location in the bytecode it emits). Stefan