From: Sebastian Humenda <shumenda@gmx.de>
To: edbrowse-dev <edbrowse-dev@lists.the-brannons.com>
Subject: Re: [Edbrowse-dev] JS interpreter crashes on Google books
Date: Fri, 22 Jan 2016 14:05:06 +0100 [thread overview]
Message-ID: <20160122130506.GB2555@Kraftkrust> (raw)
In-Reply-To: <20160022074131.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
Hi,
Karl Dahlke schrieb am 22.01.2016, 7:41 -0500:
>Well gdb cuts to the heart of it, as it often does.
>The problem is in the new xhr system when cw (current window) is null.
[...]
Thanks for investigating it.
>Not sure the result is much better though.
Do you want me to test it or is a second opinion not of any help?
Cheers
Sebastian
--
Web: http://www.crustulus.de (English|Deutsch) | Blog: http://www.crustulus.de/blog
FreeDict: Free multilingual dictionaries - http://www.freedict.org
Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-22 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 12:49 Sebastian Humenda
2016-01-22 8:14 ` Karl Dahlke
2016-01-22 12:41 ` Karl Dahlke
2016-01-22 13:05 ` Sebastian Humenda [this message]
2016-01-23 1:41 ` Kevin Carhart
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=20160122130506.GB2555@Kraftkrust \
--to=shumenda@gmx.de \
--cc=edbrowse-dev@lists.the-brannons.com \
/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).