From: Karl Dahlke <email@example.com>
Subject: [Edbrowse-dev] Seeing caught errors.
Date: Mon, 19 Feb 2018 01:01:12 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
For you serious debuggers, this is crude, but might meet most of our needs most of the time.
1. I renamed dbc to dbcn, debug cloneNode.
2. I renamed dbe to dbev, debug events.
3. New toggle command dber to debug all js errors, even caught errors.
4. All of these debug messages flow within the debug stream, even if you redirect to a file.
They use to be simple prints.
5. dber prints the error and line number. To be most useful, scripts should be deminimized.
6. If the error is uncaught you'll see it twice, once from the error interceptor and once when the script aborts.
7. nasa.gov generates a lot of caught errors, not sure which ones of these are ok and which ones not.
This will be a recurrring theme.
next reply other threads:[~2018-02-19 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 6:01 Karl Dahlke [this message]
2018-02-19 23:54 ` [Edbrowse-dev] making mixed case out of inline CSS Kevin Carhart
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).