From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] js shell
Date: Sat, 08 Feb 2014 09:56:42 -0500 [thread overview]
Message-ID: <20140108095642.eklhad@comcast.net> (raw)
Again, wondering why edbrowse works with our compiled js 24 library
but not with their distributed library.
Has anyone looked at their shell application?
/usr/local/mozjs-24.2.0/js/src/shell/js.cpp
If you take this stand alone program and compile it
against the debian library does it run?
If not I would think that worthy of a bug report.
If yes then there is information there.
I did a grep for NewRuntime
and there are only a couple calls between that and NewContext,
which is the point where we segfault.
I don't think the intervening calls are important,
although SetNativeStackQuota might be,
don't know what that does.
Well it seemed like something to look at,
an application that they provide, that uses their library,
that is suppose to work.
Karl Dahlke
next reply other threads:[~2014-02-08 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 14:56 Karl Dahlke [this message]
2014-02-08 16:16 ` Chris Brannon
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=20140108095642.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).