[moving thread into the dev list]
Here's a minimal setup for reproducing the "free to wrong pool XXX not YYY during global destruction" that I experienced. It boils down to loading Storable during startup and using nfreeze() in a script. Loading Storable at startup is OK, and using nfreeze() in a script is OK, but doing both produces the error. The same thing happens with freeze() and dclone() as well (and probably other functions; haven't tested).
Most likely it's the problem Jan Dubois has mentioned here:
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2003-12/msg00994.html
If you can try and fix it that would be great (see Jan's solution). You should be able to reproduce it outside mod_perl with 'use threads and starting a thread after using nfreeze'.
__________________________________________________________________ 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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
