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: Debugging errors in bytecomp code? Date: Mon, 30 Jan 2017 23:36:10 +0530 Message-ID: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1485799585 15815 195.159.176.226 (30 Jan 2017 18:06:25 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 30 Jan 2017 18:06:25 +0000 (UTC) To: "emacs-devel@gnu.org" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 30 19:06: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 1cYGLH-0003jY-9j for ged-emacs-devel@m.gmane.org; Mon, 30 Jan 2017 19:06:15 +0100 Original-Received: from localhost ([::1]:34296 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYGLM-0005B5-N2 for ged-emacs-devel@m.gmane.org; Mon, 30 Jan 2017 13:06:20 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49066) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYGLE-0005Ai-Ns for emacs-devel@gnu.org; Mon, 30 Jan 2017 13:06:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cYGLE-0007BQ-1f for emacs-devel@gnu.org; Mon, 30 Jan 2017 13:06:12 -0500 Original-Received: from mail-yb0-x22e.google.com ([2607:f8b0:4002:c09::22e]:35886) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cYGLD-0007B2-U3 for emacs-devel@gnu.org; Mon, 30 Jan 2017 13:06:11 -0500 Original-Received: by mail-yb0-x22e.google.com with SMTP id 123so99327872ybe.3 for ; Mon, 30 Jan 2017 10:06:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=zqN0MXLkVqAlHLDOT8ksxzD4yYwm1932usZn/ykQjg8=; b=Figv6kWpjqIZTfBbLfUAxJaecqHCEEDLZbRjDzFuCqF3sNV2v0doQAxrIJ+ssKv69t Un+0NSDK813SfbOk+sbStJbKSVx8lcUwXMx6SQFf4+aYq9AQ1XMVcq1rPwoX7L269H/W n1LEaGnn0C2ZkqQ8JBGl9LFx2A71BCocj4G0eSQpSxLHsMqWG8wH0EiYsbNuSotWRijn npbbPFvUeX8mFe/n//XMQIdL6EHoblXbRHSYA1/zwlivumliHHBxcm8AdDqGdiDlfBkS nHlMQXMQKk+4vNwZj5bYqyW4AYQGfWChgY0cmP8PyHJNMsJgWlvzRZhq5JcXlxyUpYBn t66Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=zqN0MXLkVqAlHLDOT8ksxzD4yYwm1932usZn/ykQjg8=; b=h5xaLpfYv+/DhEhVnzp1s+3mJ5EhYtPhmaUrq+9g1zrUJxzmeVUR0S+1Zwtv+QHTDg V3hrx3zt3ndt037elTRTRn3og4PFsOyxXfgS7Or/oDwmS0ZZ6XLT+bj56G2xBXu23sC8 oRsFOsYCQ4ltmUoQzSD9B30HkhtLq/mAIxqVIP/DUj87brxuiyogWiKC92oruwKEjJsD EqZ6Qunl4qrekbgD2RC+6B0QpC5gXGEU+unPBYNiqCl8dIFJwlYt1Omzrbec5Bu0whoE uKqt681//+zqyepTCFcA7rrTQXK2I9TsfI0norZPPuidoxUnGtYlqfIBoWjSgoQh3abz m9cQ== X-Gm-Message-State: AIkVDXKiCei6M5pXerF2aUWXz1DLcwGfi9UGGM+z51iD/o50bH/kofReXCpUe7RmffzfMWYN9KnT0UxE4/vPsw== X-Received: by 10.37.211.20 with SMTP id e20mr11171628ybf.99.1485799571010; Mon, 30 Jan 2017 10:06:11 -0800 (PST) Original-Received: by 10.129.153.77 with HTTP; Mon, 30 Jan 2017 10:06:10 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4002:c09::22e 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:211775 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. -- Vibhav Pant vibhavp@gmail.com