From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] URL assert
Date: Wed, 23 Apr 2014 14:54:39 +0000 [thread overview]
Message-ID: <20140323145439.eklhad@comcast.net> (raw)
Yes the URL class is a royal pain.
See jsrt line 537 for all the stuff it's suppose to do.
Lots of side effects, lots of setters.
If you find a reproducible pathway to make the assert happen
I'll track through the code and look for something amiss.
I don't have a debug version build, but the regular version from Redhat
I can't get to fail, and I've tried running large blocks
of my jsrt code in a loop 100,000 times over and it seems to work.
So I guess I'm just not hitting the right combination.
I have no changes pending, nothing in work.
Chris is working on something but it's all over in sendmail.c land.
So if you do have time and want to investigate, the *cpp files are quiescent.
If other things are going on in your world I understand;
maybe you can just make the assert happen and I'll take it from there.
Cheers,
Karl Dahlke
next reply other threads:[~2014-04-23 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 14:54 Karl Dahlke [this message]
2014-04-24 9:02 ` Adam Thompson
2014-04-24 14:40 Karl Dahlke
2014-04-25 14:27 ` Adam Thompson
2014-04-25 11:25 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=20140323145439.eklhad@comcast.net \
--to=eklhad@comcast.net \
--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).