On Wed, Feb 19, 2014 at 11:38:07AM +0000, Adam Thompson wrote: > On Wed, Feb 19, 2014 at 04:21:37AM -0500, Karl Dahlke wrote: > > While doing this, I was looking at my edbrowse wiki article, > > putting in more feature content as Adam suggested, > > and I was verifying some of the internal wiki links, > > and got a segfault. > Oops, should have debugged fully first. > Looks like it's the currently being addressed lack of error checking in > jsloc.cpp which is to blame here. > This is currently being fixed.
Ok, fixed (and pushed fixes for) much of this, as well as fixing freeJavaContext so it correctly handles compartments (where correct = not failing asserts in my debug build of mozjs 24). I'm now seeing a segfault in encodeTags relating to a stringAndChar call. I'm having a go at debugging this, but it's a realloc segfault so I think I'll have to look at it in valgrind to work out why it's exploding. Cheers, Adam. _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
