> Before I go ahead and check that in, I'd like to at least get a bit more > feedback from the other folks that had been seeing this segfault, and > confirmation that this patch _does_ get rid of it.
I'll give it a whirl tonight. in truth, though, I forget exactly the conditions that were causing it - I'm seeing a segfault now with 2.0.47 (and not 2.0.52) worker in the filter tests that is not reproducable when they are run on their own. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
