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]  Frameset crash
Date: Mon, 07 Sep 2015 10:53:16 -0400	[thread overview]
Message-ID: <20150807105316.eklhad@comcast.net> (raw)
In-Reply-To: <55ECDE40.4050404@pcdesk.net>

Yeah the problem here is there's no <body> and I was traversing the body.
Kevin showed me a way around it, if body is null then traverse the root,
which contains the frameset, and that fixed the seg fault,
but the head was scanned twice, as it is under the root,
which leads to the slap-your-forehead moment of saying,
"Gee, let's start at the root."
Then everything works fine, all the time.
I have made this push.

By the way, with js turned off, and other variables out of the way,
the tidy5 parser is ten times as fast as mine.
It probably uses lex and yacc,
or techniques therefrom, which are honed for efficiency.

Karl Dahlke

  reply	other threads:[~2015-09-07 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07  0:45 Tyler Spivey
2015-09-07 14:53 ` Karl Dahlke [this message]
2015-09-07 23:40   ` 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=20150807105316.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).