[Edbrowse-dev] Seeing caught errors.

[Karl Dahlke <eklhad@comcast.net>]

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.

Karl Dahlke