From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from homiemail-a75.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by che.dreamhost.com (Postfix) with ESMTP id 1243CFE98 for ; Tue, 29 Mar 2011 06:48:57 -0700 (PDT) Received: from homiemail-a75.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a75.g.dreamhost.com (Postfix) with ESMTP id 0DF9C5EC081 for ; Tue, 29 Mar 2011 06:34:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=the-brannons.com; h=date:from:to :subject:message-id:mime-version:content-type: content-transfer-encoding; q=dns; s=the-brannons.com; b=df3a4BtI X26oS8rJ0UXW6a1yMqtrRv4XKi/QHtoOPPFmGmK3zAsjosIMbl9uwud3WwfRIOAm DM41FS1vBPYz/0Xt/KYUDh9i2Q7OGy2wsRJWOk3n13997XxLn7YCHyotpF4ijJ6O DOoaJe1YJFL+Y5bkcWpEETY50ShA05v5vRg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=the-brannons.com; h=date :from:to:subject:message-id:mime-version:content-type: content-transfer-encoding; s=the-brannons.com; bh=QPrlrfMu3QSZdC I49GTerG5pXS4=; b=GF1tQ+R3MN7fQbnjs2oRjFbsq2RgUdt7NVQmlLef1+Cbrz oQ2NOi660cdGXGzJIyVwoqRFLaPhkhH7Z+DwOduCbmiYkrsy/+y98+0jZ0blHiIW IvR/+6NVPbM0HnIpGPKQUBqT/YcGUZQ4eZInJvN4WNlGOHfK93TP6qnvxiH3s= Received: from localhost.localdomain (ip68-12-125-253.ok.ok.cox.net [68.12.125.253]) (Authenticated sender: chris@the-brannons.com) by homiemail-a75.g.dreamhost.com (Postfix) with ESMTPA id B98FF5EC069 for ; Tue, 29 Mar 2011 06:34:23 -0700 (PDT) Date: Tue, 29 Mar 2011 13:34:23 +0000 From: Christopher Brannon To: edbrowse-dev@lists.the-brannons.com Message-ID: <4d91dfdf.ctdLU5CwwefWv757%chris@the-brannons.com> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Edbrowse-dev] segfault X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.14 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2011 13:48:57 -0000 Ok, I managed to reproduce this on another machine. I have a vague idea of what the problem is. It's in the way Spidermonkey is storing strings. Apparently, on the systems which are failing, Spidermonkey was built with JS_C_STRINGS_ARE_UTF8. When Spidermonkey gets a string which isn't valid UTF8, it segfaults. The problem is that I don't know how to detect whether a given installation of Spidermonkey was compiled this way. As far as I know, it's a compile-time setting, and there is no way to detect it at runtime.