From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Stack overflow in regexp matcher
Date: Tue, 11 Aug 2009 13:22:30 -0700 [thread overview]
Message-ID: <1250021966-sup-933@masanjin.net> (raw)
In-Reply-To: <92457f310908030116k146a901aleee95a09db907d97@mail.gmail.com>
Hi Mark,
Reformatted excerpts from Mark Drayton's message of 2009-08-03:
> ## read 440m (about 52%) @ 2.2m/s. 0:03:19 elapsed, about 0:03:03 remaining
> Stack overflow in regexp matcher:
> /,\s*(?=(?:[^"]*"[^"]*")*(?![^"]*"))/ (RegexpError)
Interesting. Looks like Sup is trying to split a header line into
multiple email addresses and something's causing it to bomb. Are you
able to identify the line that's causing this problem? That would be
helpful to know.
> This error seems to have cropped up in other software so I suspect
> it's a problem with Ruby, not sup. Anyone able to confirm this?
It's a problem with Ruby's regular expression implementation, I suppose,
but we've never seen it before. The solution is to either tweak the
regexp until it starts working, or implement a custom parsing solution,
neither of which sounds that entertaining...
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-08-11 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 8:16 Mark Drayton
2009-08-11 20:22 ` William Morgan [this message]
2009-08-12 8:45 ` Mark Drayton
2009-08-16 21:43 ` William Morgan
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=1250021966-sup-933@masanjin.net \
--to=wmorgan-sup@masanjin.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