edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] 24
Date: Wed, 05 Feb 2014 20:35:52 -0800	[thread overview]
Message-ID: <87txcchn87.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140105212424.eklhad@comcast.net> (Karl Dahlke's message of "Wed, 05 Feb 2014 21:24:24 -0500")

Karl Dahlke <eklhad@comcast.net> writes:

>> I also need to work out why the debian mozjs24d package causes edbrowse
>> to just segfault on startup whereas a manually compiled one doesn't

It fails in a function called indirectly from JS_NewContext.  The
failure seems to be in mozilla::HashBytes.  For some odd reason, I can't
trace that function with gdb, even though I have debugging symbols
compiled in.

-- Chris

  reply	other threads:[~2014-02-06  4:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06  2:24 Karl Dahlke
2014-02-06  4:35 ` Chris Brannon [this message]
2014-02-06 10:34   ` Adam Thompson
2014-02-06 15:29     ` Chris Brannon
2014-02-06 18:03       ` Adam Thompson
2014-02-06 20:05         ` Chris Brannon
2014-02-06 22:03           ` Adam Thompson
2014-02-06 23:39             ` Chris Brannon
2014-02-07  8:10               ` Adam Thompson

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=87txcchn87.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --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).