From: mark@markdrayton.info (Mark Drayton)
Subject: [sup-talk] Stack overflow in regexp matcher
Date: Wed, 12 Aug 2009 09:45:01 +0100 [thread overview]
Message-ID: <92457f310908120145n453d6639mf22fe68b62054392@mail.gmail.com> (raw)
In-Reply-To: <1250021966-sup-933@masanjin.net>
Hi William
On Tue, Aug 11, 2009 at 9:22 PM, William Morgan<wmorgan-sup at masanjin.net> wrote:
> 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.
Sorry, I should have dug a bit deeper before reporting this. I was
naively assuming it was a known problem (though Google didn't know, so
I guess it's not) and that the answer would be "upgrade foo".
The line it's choking on is 284058 bytes long and contains ~6400
addresses. (gotta love mail from "internal communications"). If I
halve the number of addresses it works, so perhaps this isn't worth
fixing at all. If you do want to tackle it I'm happy to help off-list.
Cheers,
Mark
next prev parent reply other threads:[~2009-08-12 8:45 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
2009-08-12 8:45 ` Mark Drayton [this message]
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=92457f310908120145n453d6639mf22fe68b62054392@mail.gmail.com \
--to=mark@markdrayton.info \
/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