From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] repeatable seg fault
Date: Thu, 23 Jan 2014 11:06:55 +0000 [thread overview]
Message-ID: <20140123110655.GA17097@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140023050902.eklhad@comcast.net>
On Thu, Jan 23, 2014 at 05:09:02AM -0500, Karl Dahlke wrote:
> It's hard to find one that is repeatable every time, but this one is,
> at least on my box.
> Browse this url straight up and it blows up.
>
> http://www.youtube.com/user/NASAtelevision
I can confirm that this happens in my version of edbrowse as well.
According to gdb, the bug happens deep in the js library,
but the initial function call which seems to start the problem is at
html.c:2020:
onloadGo(jwin, 0, "window");
I'm not too sure why this is blowing up yet, but it looks like it's an event handler issue.
Any ideas?
Cheers,
Adam.
next prev parent reply other threads:[~2014-01-23 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 10:09 Karl Dahlke
2014-01-23 11:06 ` Adam Thompson [this message]
2014-01-23 15:16 ` Chris Brannon
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=20140123110655.GA17097@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).