From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] 24
Date: Thu, 6 Feb 2014 18:03:22 +0000 [thread overview]
Message-ID: <20140206180322.GW32200@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <87lhxogszh.fsf@mushroom.PK5001Z>
On Thu, Feb 06, 2014 at 07:29:06AM -0800, Chris Brannon wrote:
> 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.
Nice, didn't think of that.
> But the optimizations still make mozilla::HashBytes untraceable.
That's annoying.
> > 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
Ok. Is this the same as the smjs example (will look through later)?
If so, then that's definitely a debian bug and should probably be reported as
such, unless they provide a js-config script,
pkg-config .pc file or docs about this in their readme.
I'll look into this.
If any of these are provided I wonder if they provide the correct flags?
Cheers,
Adam.
next prev parent reply other threads:[~2014-02-06 18:04 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
2014-02-06 10:34 ` Adam Thompson
2014-02-06 15:29 ` Chris Brannon
2014-02-06 18:03 ` Adam Thompson [this message]
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=20140206180322.GW32200@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chris@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).