From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] deobfuscate(js_text)
Date: Thu, 23 Jun 2016 03:13:36 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1606230258020.22893@carhart.net> (raw)
In-Reply-To: <20160522082422.eklhad@comcast.net>
Hi Karl and Chuck
Well, it turns out that part two of my message was a false alarm.
Reformatting does not have a mysterious effect on parsing after all, I
just had a confounding variable at the same time. Anyway,
the incorporation of the python beautifier, in the first place, is the
real news! There is indeed a coherent change in the line number for the
bug I was describing, from
$(..) in line 1
to something like
$(..) in line 5017
That's what I was hoping for - I'm still someplace in the middle with
fastmail, but making extra progress as a result of the line numbers!
> Course I would expect a syntax error, not a type error.
Yes, it may be one of those things where the reported cause for runtimes
is skewed relative to what is actually going on. As a matter of fact, I
was thinking recently that when I sit down with pages' worth of edbrowse
output from the higher debug levels, I am generally starting at the
bottom, which may be a mistake. It suddenly hit me that runtimes in these
web pages may be a little like the compilation errors from gcc or
something! Maybe there is a cascading effect, and the errors lower down
are side effects of the first few. So I should be going to the root cause
and starting with the first thing first. I discovered that it makes a
nice debug mode if I add some exit(0) statements to readMessage in ebjs.c.
So this way, the whole program will quit on the very first error, which
forces me to address things in the order they occur.
K
prev parent reply other threads:[~2016-06-23 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 1:45 [Edbrowse-dev] a technique for the find-and-fix Kevin Carhart
2016-06-22 1:18 ` [Edbrowse-dev] deobfuscate(js_text) Kevin Carhart
2016-06-22 11:54 ` [Edbrowse-dev] OT: Fastmail and the good old days Chuck Hallenbeck
2016-06-22 12:11 ` [Edbrowse-dev] OT: Fastmail and the good old days (correction) Chuck Hallenbeck
2016-06-23 10:26 ` Kevin Carhart
2016-06-22 12:24 ` [Edbrowse-dev] deobfuscate(js_text) Karl Dahlke
2016-06-23 10:13 ` Kevin Carhart [this message]
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=alpine.LRH.2.03.1606230258020.22893@carhart.net \
--to=kevin@carhart.net \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.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).