[don't forget to always reply to the list]
Dominique Quatravaux wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Stas Bekman wrote:
| what test has caused the segfault? can you do the verbose run of | that test?
Well I was able to reproduce that failure mode only twice, but one another run gave me a deep recursion in Compress::Zlib. So I recompiled Compress::Zlib from CPAN for the heck of it from CPAN and all my problems went away. Doh!
| Dominique Quatravaux wrote: | |> Apache 2 SEGVs during the test run (see core dump at the end), |> then tests fail randomly (Failed 23/221 test scripts, [...] |> 77/2272 subtests).
I recompiled HTML::Parser and those went mostly away too. Double doh! Sorry for the fuss then.
OK, now I remember what the trace like you've posted:
(gdb) bt #0 0x4030d4d1 in __read_nocancel () from /lib/tls/libpthread.so.0 #1 0x00000000 in ?? ()
means. It means that you've build your modules with ithreads enabled perl. Then you have built a new perl *without* ithreads. But you didn't nuke the old modules. Now when you try to run those, you get the above segfault. Certainly forcing a recompile of those solves the problem, as you've reported.
I've had a hell of segfaults when Mandrake cooker recently switched to a non-threaded perl (I had all Mandrake tools segfaulting, wtih the backtrace above).
I still have a few test failures in t/apache/content_length_header.t (2 5 17), should I report those? (Basically my borged Apache from backports.org seems to behave like a 2.1 version, because if I reverse the test condition accordingly on lines 67 and 68 then tests 2 and 5 start working OK).
Certainly.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
