public inbox for edbrowse-dev@edbrowse.org
 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: Thu, 06 Feb 2014 07:29:06 -0800	[thread overview]
Message-ID: <87lhxogszh.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140206103404.GS32200@toaster.adamthompson.me.uk> (Adam Thompson's message of "Thu, 6 Feb 2014 10:34:04 +0000")

Adam Thompson <arthompson1990@gmail.com> writes:

> Yeah, the debian package's debugging symbols reference iceweasel source which
> isn't in the package (and at any rate the reference is to /tmp).

That's easy.
mkdir /tmp/buildd
cd /tmp/buildd
apt-get source libmozjs
And now you can step through the mozjs source.
But the optimizations still make mozilla::HashBytes untraceable.

> Should this be reported as a bug against the package,

I honestly don't know.  I've had problems with Debian's spidermonkey
package in the past.  Years ago, to compile on Debian, I had to pass a C
preprocessor define, so that the layout of Spidermonkey structs was the
same as the one Debian was using.  -DMOZILLA_1_8_BRANCH, I think it
was.  I wouldn't be surprised if there was an issue in their package,
but I really don't know for sure.
I also tried compiling a "Hello world" spidermonkey application, and it
segfaults in the same place.  Here it is:
http://the-brannons.com/jshello.cpp

-- Chris

  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Karl Dahlke
 ` Chris Brannon
   ` Adam Thompson
     ` Chris Brannon [this message]
       ` Adam Thompson
         ` Chris Brannon
           ` Adam Thompson
             ` Chris Brannon
               ` 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=87lhxogszh.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 read-only IMAP folder(s) and NNTP newsgroup(s).