bruce_sears has asked for the wisdom of the Perl Monks concerning the following question:

Has anyone seen anything like the following stack trace, output by my apache/mod_perl server after a crash (I think):
*** glibc detected *** /var/www/cgi-bi: munmap_chunk(): invalid pointe +r: 0x00002aaaab6e34a0 *** ======= Backtrace: ========= /lib64/libc.so.6(cfree+0x166)[0x2b8dc0619886] /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_ +sv_clear+0x6d5)[0x2b8dc921ba75] /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_ +sv_free+0x80)[0x2b8dc921bbc0] /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_ +av_clear+0x85)[0x2b8dc920da05] /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/auto/DBD/Or +acle/Oracle.so(ora_st_execute+0x284)[0x2b8dd3e4eed4] /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/auto/DBD/Or +acle/Oracle.so(XS_DBD__Oracle__st_execute+0xec)[0x2b8dd3e4167c] /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/auto/DBI/DB +I.so(XS_DBI_dispatch+0x2091)[0x2b8dd275ef81] /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_ +pp_entersub+0x3f6)[0x2b8dc9216a96] /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_ +runops_standard+0xe)[0x2b8dc921033e] /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so(Perl_ +call_sv+0x650)[0x2b8dc91bd6f0] /etc/httpd/modules/mod_perl.so(modperl_callback+0x167)[0x2b8dc8f64f87] /etc/httpd/modules/mod_perl.so(modperl_callback_run_handlers+0x30f)[0x +2b8dc8f6569f] /etc/httpd/modules/mod_perl.so(modperl_callback_per_dir+0x2f)[0x2b8dc8 +f65bef] /etc/httpd/modules/mod_perl.so[0x2b8dc8f5fb80] /etc/httpd/modules/mod_perl.so(modperl_response_handler_cgi+0x173)[0x2 +b8dc8f5fd43] /var/www/cgi-bi(ap_run_handler+0x7a)[0x2b8dbe6ada4a] /var/www/cgi-bi(ap_invoke_handler+0x72)[0x2b8dbe6b0ec2] /var/www/cgi-bi(ap_process_request+0x1a8)[0x2b8dbe6bb958] /var/www/cgi-bi[0x2b8dbe6b8b90] /var/www/cgi-bi(ap_run_process_connection+0x72)[0x2b8dbe6b4cb2] /var/www/cgi-bi[0x2b8dbe6bf7a9] /var/www/cgi-bi[0x2b8dbe6bfa3a] /var/www/cgi-bi(ap_mpm_run+0x78d)[0x2b8dbe6c029d] /var/www/cgi-bi(main+0x7e8)[0x2b8dbe69ae48] /lib64/libc.so.6(__libc_start_main+0xf4)[0x2b8dc05c4994] /var/www/cgi-bi[0x2b8dbe69a199] ======= Memory map: ======== 401bc000-401bd000 ---p 401bc000 00:00 0 401bd000-401cc000 rwxp 401bd000 00:00 0 2aaaaaab4000-2aaaaac2a000 rw-p 2aaaaaab4000 00:00 0 2aaaaac2b000-2aaaaac2d000 r-xp 00000000 fd:00 9867565 + /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/auto/AP +R/Status/Status.so 2aaaaac2d000-2aaaaae2c000 ---p 00002000 fd:00 9867565 + /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/auto/AP +R/Status/Status.so . . . [would more memeory map be useful here?]
It looks like it is an invalid pointer to some object that is queued up to be deallocated memory (?)

much appreciated, any response.

Bruce

p.s. sorry if this is more apache than perl. not sure.

UPDATE I have inklings that this may be a 32 bit vs 64 bit compatibility issue where mod_perl and installed perl modules are not playing well together. And it does not appear to be specific to DBD::Oracle. That's probably a red herring.