On Thu, Feb 06, 2014 at 07:29:06AM -0800, Chris Brannon wrote:
> Adam Thompson <[email protected]> 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.
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev

Reply via email to