From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Vibhav Pant Newsgroups: gmane.emacs.devel Subject: Re: Debugging errors in bytecomp code? Date: Tue, 31 Jan 2017 22:20:56 +0530 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1485884596 5543 195.159.176.226 (31 Jan 2017 17:43:16 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2017 17:43:16 +0000 (UTC) Cc: "emacs-devel@gnu.org" To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 31 18:43:12 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 1cYcSW-00018B-1R for ged-emacs-devel@m.gmane.org; Tue, 31 Jan 2017 18:43:12 +0100 Original-Received: from localhost ([::1]:39790 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYcSZ-0001a8-M0 for ged-emacs-devel@m.gmane.org; Tue, 31 Jan 2017 12:43:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53216) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYbdz-0002f1-CG for emacs-devel@gnu.org; Tue, 31 Jan 2017 11:51:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cYbdy-0000sN-L0 for emacs-devel@gnu.org; Tue, 31 Jan 2017 11:50:59 -0500 Original-Received: from mail-yb0-x235.google.com ([2607:f8b0:4002:c09::235]:33656) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cYbdy-0000rb-Gx for emacs-devel@gnu.org; Tue, 31 Jan 2017 11:50:58 -0500 Original-Received: by mail-yb0-x235.google.com with SMTP id w194so230001818ybe.0 for ; Tue, 31 Jan 2017 08:50:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TNQ4HMheTK3/sJA8TNntLWomb9EL6Laq3ttCxWe2ps0=; b=oKAJ+ezDUeP08xR1zXz1jl+BEMbUXgX/hzNgTAf0ogaf9L6Rz6BH4gCVyvS9tWEy1u CYCm8+3EI9XsA3TWUQMhsASqliWUBRhGV75NoP6jfYYWNAMH9tnYzd1D1C8CNWtBJDIi S45ovl9wMJRgLmTJRPZuruAZ2mgUmrck3X/o2ZDbKBJ0BZZAMDrIS3OP/o6DAjN3AhzS lqQt352v6c17q0epmmtfdgmZneGxqp08H1XDB6kb87jjk6llQgI2Vuoh/GNphbKjZucV p/gOSF2gxv48mJMkAuP8qV4WbsQa8mxYHj/AyCK53u9MsAwFEexcW5x/XPKJYSCf0Nfd HUPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TNQ4HMheTK3/sJA8TNntLWomb9EL6Laq3ttCxWe2ps0=; b=QaLzmxqaykASgHgErIE4Qq8Z9goSab5TdyLu5vo9HBLV2PMOnqBJ6PSpUtutDtpPXw NcwLk6vtFKF8jrJAVyQBR1Raqyd83q2/4LjmVQ4mmLR19x5tPCLCY5AT0UnKpagMJaip NA15cUNKUdUAgQx+U43pSV2L818ztKc0I0b8PnTlbiPXBdCrXawUUjbZLYfn/mKOrf8J Lim9FVIX25p0Z3myGpXCtJZBmCHPtGMCS1x3Im5nrEiIYPBDSWaC+WfWn5SB5XZfKXPv ROvB0mP+fCVum0X8j0vxGzjJcOnB/lDZL5K3vj90UFdOUde0d5u9RkpO/+60uNpKmRSa ix1g== X-Gm-Message-State: AIkVDXLj5vhxAAyoi3bQPs49eFlPSdTy8wYIVVmeEs44JeJOJQ9Hu35+p+RAxsTWw+MkFqaAnyzTGkz2zG6DFw== X-Received: by 10.129.174.90 with SMTP id g26mr21713591ywk.25.1485881457492; Tue, 31 Jan 2017 08:50:57 -0800 (PST) Original-Received: by 10.129.153.77 with HTTP; Tue, 31 Jan 2017 08:50:56 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4002:c09::235 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:211806 Archived-At: ah, thanks. On Tue, Jan 31, 2017 at 8:02 PM, Stefan Monnier wrote: >> 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 > > -- Vibhav Pant vibhavp@gmail.com