From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Encouraged, Discouraged
Date: Wed, 24 Dec 2014 14:21:03 -0500 [thread overview]
Message-ID: <20141124142103.eklhad@comcast.net> (raw)
Well the new edbrowse almost works.
I'm encouraged that it does anything at all.
I really thought it would seg fault straight away.
It's simpler in so many ways.
There is only one line that enters the compartment,
the entry point to processing the message.
jseng-moz.cpp line 2543
Remember the old system, we had no idea what functions
were called when, no idea the order of execution,
so we put AutoCompartment in practically every function.
No need for all that confusion any more.
So it mostly works, but not quite.
I have a test program
http://www.eklhad.net/jf
browse it and it is missing half its stuff.
But, in ebjs.c, after line 1014, add this
has_property(cw->docobj, "all");
Then edbrowse works properly.
jf has all the properties and objects that it should have.
Why should that call matter?
It's almost as inocuous as a debug print.
I hate interactions like that.
So I'm a bit discouraged to be this close and not there.
I think I need to take a break from this for a while.
We've made really good progress though.
Karl Dahlke
reply other threads:[~2014-12-24 19:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141124142103.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).