From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by hurricane.the-brannons.com (Postfix) with ESMTP id B127B7842C for ; Sat, 8 Feb 2014 06:57:18 -0800 (PST) Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta05.westchester.pa.mail.comcast.net with comcast id Pqmj1n0030vyq2s55qwiv6; Sat, 08 Feb 2014 14:56:42 +0000 Received: from eklhad ([107.5.36.150]) by omta05.westchester.pa.mail.comcast.net with comcast id Pqwi1n00M3EMmQj3RqwiJc; Sat, 08 Feb 2014 14:56:42 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Sat, 08 Feb 2014 09:56:42 -0500 Message-ID: <20140108095642.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1391871402; bh=1MjRc2BATLS3kMBv1ZBPgXdM/d0WaVTsiUXB8CTEZdI=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=Q1ZN52uO0JrFebwOwnLlBckt4pVqvlFSKO24Y5JKag4mHfOeIoMUXJZPzYke1GA8p yxgnQfUUV9qbfjA0jmIDqEdGTqSzGb4iJ7/G1GIWJdv/WZuZx3ElPkb3Grkvr8LJ30 yy2OOY8Ye4R4sbNMhqCUz3fRZuweCamhjfj+aOfmnlc1dRHEyPxKSsOMoc4NZMgzNx zVXQkpG9bRvIAz6r4WeK0PQR9CZMkBhsdtwJ8AGgyKfOdfYwDL+Kk7vz+a3lFnihyA 6NO+J9a43XrMGSxIp5h1kZuds0vaEegilNDiEaG009SVxfCcH93ztKvrZXS/z9jss/ 1Skp1d52DuW5g== Subject: [Edbrowse-dev] js shell X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Karl Dahlke List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Feb 2014 14:57:19 -0000 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