From: Chris Brannon <chris@the-brannons.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] bad byte in NASA's vendor.js
Date: Thu, 29 Dec 2016 18:11:03 -0800 [thread overview]
Message-ID: <8760m2w4i0.fsf@the-brannons.com> (raw)
In-Reply-To: <alpine.LRH.2.03.1612291703430.7749@carhart.net> (Kevin Carhart's message of "Thu, 29 Dec 2016 17:30:00 -0800 (PST)")
Kevin Carhart <kevin@carhart.net> 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
next prev parent reply other threads:[~2016-12-30 2:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 1:30 Kevin Carhart
2016-12-30 2:11 ` Chris Brannon [this message]
2016-12-30 3:24 ` Karl Dahlke
2016-12-30 18:52 ` Chris Brannon
2016-12-30 19:58 ` Karl Dahlke
2016-12-30 20:07 ` Chris Brannon
2016-12-30 23:13 ` Karl Dahlke
2016-12-31 5:28 ` Kevin Carhart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760m2w4i0.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=kevin@carhart.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).