From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (unknown [IPv6:2602:4b:a4a9:e100::63a:26e7]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id ED16B7913E; Thu, 29 Dec 2016 18:11:35 -0800 (PST) From: Chris Brannon To: Kevin Carhart Cc: Edbrowse-dev@lists.the-brannons.com References: Date: Thu, 29 Dec 2016 18:11:03 -0800 In-Reply-To: (Kevin Carhart's message of "Thu, 29 Dec 2016 17:30:00 -0800 (PST)") Message-ID: <8760m2w4i0.fsf@the-brannons.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] bad byte in NASA's vendor.js 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: Fri, 30 Dec 2016 02:11:36 -0000 Kevin Carhart writes: > Wow! I found something that can cause JS to crash, yet is more to do > with our retrieval of javascript code files as large ascii files, > rather than javascript-the-language. Simplest testcase, http://the-brannons.com/jsbytes.html. When we have a fix, we should add it to jsrt. I'm not quite sure where the mixup is happening, because as far as I can tell from db5, the correct byte sequence is going to JS. -- Chris