Excerpts from Edward Z. Yang's message of Fri Jun 05 01:08:10 -0400 2009: > I tickled the bug and took a more careful look at the message that had > triggered it, and noticed that it was an auto-generated commit message > that was really long. So one possible stop-gap would be just to detect > if a message is long and disable quoting if that was the case (a long > message would be, say, one over 100KB). There is also a possibility > that the commit message had some pathological backtracking built into > it.
I think I'm experiencing a similar problem with long messages which sometimes get generated by chrootkit. I've cleverly deleted (rather than moving somewhere innocuous) all such messages to get sup past the chokepoint, but I expect a new one will be generated this weekend and I'd be happy to look at it. I noticed that one feature of the messages was that they contained one extremely long line. Not sure if this information will in any way help figure out what's going on there.
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
