From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] adding javascript enable to netsurf
Date: Wed, 11 Mar 2020 19:27:17 +0900 [thread overview]
Message-ID: <24A4F159EACDA551F4C84CB651D9C293@hera.eonet.ne.jp> (raw)
In-Reply-To: 80e9edc42326584c4073d484bef78e14@oboj.net
[-- Attachment #1: Type: text/plain, Size: 74 bytes --]
Thanks a lot!
Yes, it seems to hit my case.
I'll see it tommorow.
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 3584 bytes --]
From: jamos@oboj.net
To: 9front@9front.org
Cc: kokamoto@hera.eonet.ne.jp
Subject: Re: [9front] adding javascript enable to netsurf
Date: Wed, 11 Mar 2020 10:29:03 +0100
Message-ID: <80e9edc42326584c4073d484bef78e14@oboj.net>
Reverse engineering a Linux executable, there is indeed a
javascript_init() defined. It looks like it comes form the
following object file:
nm netsurf/build/Linux-gtk/content_handlers_javascript_content.o | grep
javascript_init
0000000000000150 T javascript_init
I cannot either find the proper declaration for the function
in the source, but maybe it is autogenerated somehow. In
'netsurf/content/content_factory.h' I find the macro:
#define CONTENT_FACTORY_REGISTER_TYPES(HNAME, HTYPELIST, HHANDLER)
\
nserror HNAME##_init(void) { … }
That is used in 'netsurf/content/handlers/javascript/content.c':
CONTENT_FACTORY_REGISTER_TYPES(javascript, javascript_types,
javascript_content_handler);
I don’t have the time right now to investigate further, but maybe
those findings can lead you a bit further. Duktape can be
enabled/disabled both in compile time and runtime too, I think.
Jonas
On 2020-03-11 07:36, kokamoto@hera.eonet.ne.jp wrote:
> I'm still struggling this.
> Error message says:
> javascript_init: redifinition: javascript_init
> (4481) TEXT javascript_init t0(SB). R0, $16
>
> javascript_init is declared only once in
> ./netsurf/content/handlers/javascript/content.h:
> nserror javascript_init(void);
>
> However, I cannot find the body of that function anywhere...
>
> The javascript_init is called from
> ./netsurf/content/handlers/javascript/duktape/dukky.c like:
>
> /* exported interface documented in js.h */
> void js_initialise(void)
> {
> /** TODO: Forces JS on for our testing, needs changing before a release
> * lest we incur the wrath of others.
> */
> /* Disabled force-on for forthcoming release */
> /* nsoption_set_bool(enable_javascript, true);
> */
> javascript_init(); <====
> }
>
> Please let me know the meaning of that comment, I'm not native English
> user,
> then, it is difficult to understand why then javascript_init() is used
> here...
>
> Kenji
next reply other threads:[~2020-03-11 10:27 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 10:27 kokamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-14 5:04 kokamoto
2020-04-14 21:53 ` Kyle Nusbaum
2020-04-15 20:05 ` jamos
2020-04-15 20:24 ` ori
2020-04-18 1:09 ` Kyle Nusbaum
2020-04-18 1:19 ` ori
2020-04-18 17:11 ` Eli Cohen
2020-04-18 17:15 ` telephil9
2020-04-18 17:17 ` ori
2020-04-13 23:46 kokamoto
2020-04-07 4:25 kokamoto
2020-04-06 5:48 kokamoto
2020-04-13 12:44 ` jamos
2020-04-05 4:52 kokamoto
2020-04-05 4:41 kokamoto
2020-03-22 23:47 kokamoto
2020-03-22 2:19 kokamoto
2020-03-21 3:24 kokamoto
2020-03-22 20:27 ` jamos
2020-03-22 20:54 ` ori
2020-03-22 20:54 ` ori
2020-03-20 5:49 kokamoto
2020-03-20 16:10 ` Kyle Nusbaum
2020-03-20 16:15 ` ori
2020-03-20 17:12 ` telephil9
2020-03-20 17:40 ` Jens Staal
2020-03-20 18:54 ` jamos
2020-03-21 5:00 ` Jens Staal
2020-03-21 12:24 ` Ethan Gardener
2020-03-20 22:07 ` Kyle Nusbaum
2020-03-17 11:16 kokamoto
2020-03-17 17:42 ` jamos
2020-03-15 9:42 kokamoto
2020-03-15 11:06 ` Steve Simon
2020-03-15 11:38 ` Jens Staal
2020-03-15 13:50 ` jamos
2020-03-14 1:49 kokamoto
2020-03-14 2:09 ` ori
2020-03-14 1:19 kokamoto
2020-03-14 1:34 ` ori
2020-03-13 4:33 kokamoto
2020-03-13 4:58 ` ori
2020-03-12 5:28 kokamoto
2020-03-12 2:20 kokamoto
2020-03-12 2:43 ` ori
2020-03-11 23:59 kokamoto
2020-03-11 6:36 kokamoto
2020-03-11 9:29 ` [9front] " jamos
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=24A4F159EACDA551F4C84CB651D9C293@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9front@9front.org \
/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).