From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Emacs-24.3 crash when browse-url Date: Tue, 04 Dec 2012 13:45:28 -0500 Message-ID: References: <87mwxuhrso.fsf@gmail.com> <87y5hd6f23.fsf@gmail.com> <87pq2p6ebj.fsf@gmail.com> <87lidd6aam.fsf@gmail.com> <87hao166im.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1354654503 2772 80.91.229.3 (4 Dec 2012 20:55:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 4 Dec 2012 20:55:03 +0000 (UTC) Cc: Andreas Schwab , emacs-devel@gnu.org To: Thierry Volpiatto Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 04 21:55:14 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TfzWH-000753-IQ for ged-emacs-devel@m.gmane.org; Tue, 04 Dec 2012 21:55:09 +0100 Original-Received: from localhost ([::1]:49836 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TfzW5-000898-HX for ged-emacs-devel@m.gmane.org; Tue, 04 Dec 2012 15:54:57 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:56218) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TfzW0-00088c-P9 for emacs-devel@gnu.org; Tue, 04 Dec 2012 15:54:55 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TfzVz-0002h7-J9 for emacs-devel@gnu.org; Tue, 04 Dec 2012 15:54:52 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:11116) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TfxUo-0002LV-8N for emacs-devel@gnu.org; Tue, 04 Dec 2012 13:45:30 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAG6Zu09soXOY/2dsb2JhbABEtBGBCIIVAQEEAScvDxQQCzQSFBgNJIgcBboJkEQDiEKacYFYgwc X-IronPort-AV: E=Sophos;i="4.75,637,1330923600"; d="scan'208";a="209069500" Original-Received: from 108-161-115-152.dsl.teksavvy.com (HELO pastel.home) ([108.161.115.152]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 04 Dec 2012 13:45:29 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 9F0D358C73; Tue, 4 Dec 2012 13:45:28 -0500 (EST) In-Reply-To: <87hao166im.fsf@gmail.com> (Thierry Volpiatto's message of "Tue, 04 Dec 2012 19:01:37 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:155262 Archived-At: >>> Debugger entered--Lisp error: (error "binding stack not balanced (serious byte compiler bug)") >>> browse-url-xdg-open("http://www.google.fr" nil) >> M-x disassemble RET browse-url-xdg-open RET > --8<---------------cut here---------------start------------->8--- > byte code for browse-url-xdg-open: > doc: Pass the specified URL to the "xdg-open" command. ... > args: (url &optional ignored) > interactive: (browse-url-interactive-arg "URL: ") > 0 constant call-process > 1 constant "xdg-open" > 2 constant nil > 3 constant 0 > 4 constant nil > 5 varref url > 6 call 5 > 7 return > --8<---------------cut here---------------end--------------->8--- Hmm... "binding stack not balanced (serious byte compiler bug)" means that the specpdl stack (the stack of things that need to be unwound, such as unwind-protects and dynamic let bindings) does not have the same height at the end of (presumably) browse-url-xdg-open as it had at the beginning. But as we see above, browse-url-xdg-open does not push nor pop anything to/from that stack (it does push constants onto the bytecode's execution stack, but that's a completely different stack). So, the specpdl stack was somehow messed up, presumably during the execution of browse-url-xdg-open but apparently not by the byte code of browse-url-xdg-open. It could be a problem in `call-process'. >> I suspect that your browse-url.elc file is somehow corrupted because >> this function is very small and simple, so there's not much opportunity >> for the byte-compiler to mess it up. > Why would it be corrupted ? No idea, it was just a shot in the dark, but the disassembly seems to indicate it's not corrupted. Stefan