Justin Mason wrote: > On Fri, Jan 29, 2010 at 14:59, Mark Martinec <mark.martinec...@ijs.si> wrote: >> On Friday 29 January 2010 04:20:15 René Berber wrote: >>> Jason Bertoch wrote: >>>> What version of re2c are you using? Can you post the output of >>>> 'spamassassin -D --lint' to pastebin? >>> Now using re2c 1.3.5 same problem, to be precise it doesn't hang, it >>> loops (the CPU usage goes up and down, RSS the same, up and down) at the >>> same point. >>> >>> Here's the output http://pastebin.com/m438000e0 >> Indeed, it looks like spinning in >> zoom: run_body_fast_scan for body_0 >> >> Could well be due to some problematic rule (SARE?), >> combined with some unusual mail. >> >> The re2c and the 'zoom:' plugins are beyond my expertise. >> I suggest you open a problem report, and attach >> your above log there, so that it does not get lost. > > +1. > > Typically the best approach is to binary-search the list of "body" > rules until you identify the subset that cause the problem, then use > "sa-compile --keep-tmps" to capture the re2c output and attach it.
About SARE, I cleaned up my configuration before running the test, perhaps I missed something because I still end up with one compiled 70_ rule. The idea about keep-temps sounds good, I could take a look at the source code produced by re2c for possible problems in the "zoom" rule(s). -- René Berber
