edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] css in C
Date: Tue, 27 Feb 2018 06:24:03 -0500	[thread overview]
Message-ID: <20180127062403.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1802270055040.20626@carhart.net>

[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]

As for debugging, I try to keep those commands in the quick reference guide under the debug section.
Though they don't include the js functions in startwindow that might help, maybe they should, maybe not, IDK,
at a philosophical level it's just the edbrowse commands.
So here is your list with some edits, the first few coming from the quick reference guide.
These work from edbrowse or within jdb.

db3 : set debug level, 0 through 9
db>/tmp/edbrowse.out : redirect debugging output to a file
jdb : javascript debugger, bye to exit
demin : deminimize javascript (toggle)
timers : disable javascript timers (toggle)
dbcn : enable cloneNode debugging (toggle)
dbev : enable event debugging (toggle)
dber : enable js error debugging (toggle)
dbcss : enable css debugging (toggle)

^> - the file redirect to your filesystem
showscripts - list all scripts
searchscripts - searches all scripts for a string
aloop

> error in f575d3.ontimer()

You have my head in a whirl with this one.
It comes from jseng-duk.c line 1790, from html.c line 2346.
So it's hex for the c pointer of the timer object that was created to run the timer,
but that object goes away once the timer has fired.
We would either have to make these timers not go away, whence they would accumulate, or perhaps print more helpful information before the timer runs.
The body attribute would be helpful, the source code for the timer,
but sometimes, perhaps most of the time, it isn't given source but rather a function.
setTimeout(f, 30000);
Hardly anything useful we can do with that.
I'll give this a little more thought.

Karl Dahlke

  reply	other threads:[~2018-02-27 11:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 19:44 Karl Dahlke
2018-02-27  9:33 ` Kevin Carhart
2018-02-27 11:24   ` Karl Dahlke [this message]
2018-02-28  0:31     ` Kevin Carhart
  -- strict thread matches above, loose matches on Subject: below --
2018-02-24 19:21 [Edbrowse-dev] css in c Karl Dahlke

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=20180127062403.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).