From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] email header screwup (and fix)
Date: Thu, 9 Sep 2010 16:13:53 -0400 [thread overview]
Message-ID: <beb5a7a5d1437be48147b1975dd37d6f@brasstown.quanstro.net> (raw)
lately, i've been seeing email with gigantic headers.
120 header lines are not that uncommon. unfortunately
upas has sometimes inserts a blank line about
(but not exactly) 4k into the file. a bit of digging, upas/send
was assuming that if yacc didn't stop at a blank line, one should
be inserted. unfortunately, yacc was stopping because it ran out of stack
space. the hack is to increase YYMAXDEPTH. ideally,
each line should be parsed independently, thus making
yacc's depth depend only on the complexity of a line.
nupas on sources has the fix.
- erik
next reply other threads:[~2010-09-09 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 20:13 erik quanstrom [this message]
2010-09-11 22:15 ` Russ Cox
2010-09-13 17:37 ` erik quanstrom
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=beb5a7a5d1437be48147b1975dd37d6f@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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).