edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] segfault with small pool
Date: Wed, 19 Feb 2014 14:12:37 +0000	[thread overview]
Message-ID: <20140219141237.GK28870@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140219113807.GJ28870@toaster.adamthompson.me.uk>

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.

  reply	other threads:[~2014-02-19 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19  9:21 Karl Dahlke
2014-02-19 11:28 ` Adam Thompson
2014-02-19 11:38 ` Adam Thompson
2014-02-19 14:12   ` Adam Thompson [this message]
2014-02-19 16:07     ` Chris Brannon
2014-02-19 16:52       ` Adam Thompson
2014-02-19 17:34         ` Chris Brannon
2014-02-19 21:04           ` Adam Thompson
2014-02-19 16:36 Karl Dahlke

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=20140219141237.GK28870@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).