On Wed, Feb 05, 2014 at 08:35:52PM -0800, Chris Brannon wrote: > Karl Dahlke <[email protected]> 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.
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). In addition, the packaged lib is compiled with optimisations making debugging... interesting... even when the debugging symbols actually work. These difficulties were the main motivation behind using my own compiled mozjs24. Should this be reported as a bug against the package, or is this segfault an edbrowse problem do you think? Cheers, Adam. PS: the mozjs26d package is still broken so no chance of building against that. _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
