Christian Hansen wrote:

Program received signal EXC_BAD_ACCESS, Could not access memory. 0x014563fc in S_mess_alloc ()

(gdb) bt
#0  0x014563fc in S_mess_alloc ()
#1  0x014566e8 in Perl_vmess ()
#2  0x014571dc in Perl_vcroak ()
#3  0x014576b8 in Perl_croak_nocontext ()
#4  0x007dd9c8 in modperl_global_cleanup ()
#5  0x006a3f60 in run_cleanups (cref=0x1806228) at apr_pools.c:1952
#6  0x006a35f4 in apr_pool_clear (pool=0xbffffa1c) at apr_pools.c:694
#7  0x0000ac34 in main (argc=11, argv=0xbffffc40) at main.c:575

Looks like I'm hitting the same problem that Philippe M. Chiasson reported last month, http://article.gmane.org/gmane.comp.apache.mod-perl/18408

Philippe, any chance you could do the promised investigation you have promised at the above URL?


I'm using trunk, revision: 169956. With 1.999.21 all tests passes, so guess something changed in the namespace change.

With the same perl and apache versions/configuration?

Please let me know if I can be at further assistance.

Christian, any difference if you test with perl w/o ithreads?

--
__________________________________________________________________
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

Reply via email to