From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out.smtp-auth.no-ip.com (out.smtp-auth.no-ip.com [8.23.224.60]) by hurricane.the-brannons.com (Postfix) with ESMTPS id B98B579EE1 for ; Fri, 13 Jan 2017 18:48:57 -0800 (PST) X-No-IP: carhart.net@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from carhart.net (unknown [99.52.200.227]) (Authenticated sender: carhart.net@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id D900E542; Fri, 13 Jan 2017 18:49:21 -0800 (PST) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id v0E2nKlY014567; Fri, 13 Jan 2017 18:49:21 -0800 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id v0E2nKil014563; Fri, 13 Jan 2017 18:49:20 -0800 Date: Fri, 13 Jan 2017 18:49:20 -0800 (PST) From: Kevin Carhart To: Chris Brannon cc: Edbrowse-dev@lists.the-brannons.com In-Reply-To: <874m12y1ki.fsf@the-brannons.com> Message-ID: References: <20170010083850.eklhad@comcast.net> <874m12y1ki.fsf@the-brannons.com> User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [Edbrowse-dev] seg fault in edbrowse proper X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2017 02:48:58 -0000 I think I noticed this. I think the "kill javascript on any javascript runtime" code from ebjs is triggered prior to the seg fault. But it's tricky to grasp what happened, because of what we've been saying in the recent messages about this ebjs code: it gets buried by the rest of the db5 output. But I think Karl just went ahead with changing this to quit eb immediately. Now, I think if you go through these motions (javascript disabled but no seg fault) you actually can indeed read Raw Story articles. So it is sort of like the right thing happening for the wrong reasons. It still could be seen as a good thing but it is capricious, because Raw Story did not happen to hold their plain text hostage to successful JS completion, but unfortunately a lot of other sites do. Kevin