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: Debugging errors in bytecomp code? Date: Tue, 31 Jan 2017 09:32:28 -0500 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1485873330 12748 195.159.176.226 (31 Jan 2017 14:35:30 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2017 14:35:30 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 31 15:35:27 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 1cYZWo-0003A8-Ot for ged-emacs-devel@m.gmane.org; Tue, 31 Jan 2017 15:35:26 +0100 Original-Received: from localhost ([::1]:38630 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYZWs-0000nP-Fv for ged-emacs-devel@m.gmane.org; Tue, 31 Jan 2017 09:35:30 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47861) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYZWe-0000kR-NE for emacs-devel@gnu.org; Tue, 31 Jan 2017 09:35:23 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cYZWZ-0004v6-R9 for emacs-devel@gnu.org; Tue, 31 Jan 2017 09:35:16 -0500 Original-Received: from [195.159.176.226] (port=60108 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cYZWZ-0004uS-K9 for emacs-devel@gnu.org; Tue, 31 Jan 2017 09:35:11 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cYZWR-0002V6-SC for emacs-devel@gnu.org; Tue, 31 Jan 2017 15:35:03 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 9 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:0m/UpLX31IewQz2puJAi3Ukxi/U= 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:211791 Archived-At: > Is there a way to enter the debugger when a error in bytecomp code > itself is encountered? Right now, all errors including compilation ones > are printed to the *Compile-Log* buffer, making it impossible to get > a backtrace for internal compiler errors. (setq byte-compiler-debug t) ? Stefan