From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33])
	by hurricane.the-brannons.com (Postfix) with ESMTPS id BAB85791CD
	for <edbrowse-dev@edbrowse.org>; Sun,  8 Dec 2019 07:26:38 -0800 (PST)
Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109])
	by resqmta-ch2-01v.sys.comcast.net with ESMTP
	id dxrJiciMKe5pqdySDiwjA2; Sun, 08 Dec 2019 15:26:37 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
	s=20190202a; t=1575818797;
	bh=vqGBka+N7RG64jK+nPgXiS8u2OesaQkTWc4JM21rans=;
	h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID:
	 Mime-Version:Content-Type;
	b=KbRNaNgXfuJ1EfdsF8eYveyeAqdA9plIG4OFvKuc2EpoNzNDc5BPP3+1Ez9gFSdeW
	 4e2IFxFM4eqaa49TFDDjOHV6bArDfOQ7aQ+WN1fa9GfUXyM9j9gGG5Zw1HXRZE5u0e
	 79nOj6X56sUpe3alhKIkFfgT1uXFQvbrUxVjppjuUCRSWRqzCLAGItGS2csRLGvBaM
	 yf6TQOUA5rxGhX2hnpFSMB2aPkxsBsYxYJDru+cmQEfi83T36vVB/yhvb+1psXYXtJ
	 Z5jgidOZ3CfieZxDPCxzgKXWJUgNJqV1zNeCUTEkx0l0Q8nLg0ss8mU4FG7XHpyZdr
	 a81MqSzmfos7Q==
Received: from unknown ([IPv6:2601:408:c300:a3d0:21e:4fff:fec2:a0f1])
	by resomta-ch2-13v.sys.comcast.net with ESMTPSA
	id dySCiLoWyfWv4dySDi3vGZ; Sun, 08 Dec 2019 15:26:37 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
To:edbrowse-dev@edbrowse.org
From: Karl Dahlke <eklhad@comcast.net>
Reply-to: Karl Dahlke <eklhad@comcast.net>
References: <20191207172853.GB194728@toaster> <20191208135333.GF194728@toaster>
User-Agent: edbrowse/3.7.6
Subject: [edbrowse-dev] Abort from within duktape when visiting...
Date: Sun, 08 Dec 2019 10:26:36 -0500
Message-ID: <20191108102636.eklhad@comcast.net>
X-BeenThere: edbrowse-dev@edbrowse.org
List-Id: Edbrowse Development List <edbrowse-dev.edbrowse.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=nextpart-eb-262545
Content-Transfer-Encoding: 7bit

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--nextpart-eb-262545
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Yes, we didn't need the 20 thousand lines of output, just the last =
line, as it does what I thought it might be doing, starting a low level =
calland not finishing it.
core dumps and gdb won't help, even if you did have the duktape =
symbols, it is a deliberate abort because of some runtime issue not =
protected.
I've sometimes thought I have to protect *every* duktape call we make, =
but so much overhead, in software and in performance.
Not sure what to do about that.
As a verification you can comment out html.c line 926 and it runs.
I don't just want to protect the call set_property_string, though I may =
have to, I'd really like to know what is going wrong here.
In jdb, try setting document.readyState =3D "complete"
This is protected so won't core dump, but neither does it show any =
errors, even with dberr, and neither does it change the value of =
readyState,
so the web page has done something to it.
either it's not a string any more (getter setter), or it is not =
writeable.

Karl Dahlke

--nextpart-eb-262545--