ID: 36246 Comment by: joe at virtualmin dot com Reported By: eustaquiorangel at yahoo dot com Status: No Feedback Bug Type: XSLT related Operating System: Linux, Slackware 10.2 (current) PHP Version: 5.1.2 New Comment:
Just an added data point: I'm getting this same crasher, but only when mod_fastcgi is enabled (not even using a PHP script--but it appears to happen when PHP is being loaded by fcgi). Here's the pseudo-backtrace from the log (I'll try to reproduce it in gdb later): *** glibc detected *** /usr/sbin/httpd: double free or corruption (fasttop): 0x09ece438 *** ======= Backtrace: ========= /lib/libc.so.6[0x560124] /lib/libc.so.6(__libc_free+0x77)[0x56065f] /etc/httpd/modules/libphp5.so(zend_hash_destroy+0x75)[0x4188587] /etc/httpd/modules/libphp5.so(sapi_shutdown+0x20)[0x414c599] /etc/httpd/modules/libphp5.so[0x41bc65c] /usr/lib/libapr-0.so.0[0xa18ed5] /usr/lib/libapr-0.so.0(apr_pool_clear+0x35)[0xa19c80] /usr/sbin/httpd(main+0x468)[0x65774b] /lib/libc.so.6(__libc_start_main+0xdf)[0x511d5f] /usr/sbin/httpd[0x649151] ======= Memory map: ======== Previous Comments: ------------------------------------------------------------------------ [2006-02-09 01:00:05] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2006-02-01 20:23:26] [EMAIL PROTECTED] Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. ------------------------------------------------------------------------ [2006-02-01 20:13:01] eustaquiorangel at yahoo dot com > We can't reproduce it, so you tell us. Too many variables there, but definitely something is different from 5.1.1 to 5.1.2. To reproduce it the way we have here you'll need the exactly the same environment, but this is a complicated matter. OS, Apache version, all the scripts needed to run our environment. As I'm trying to make this works since before yesterday, I can't wait more to put the computer to work. I'll stick with 5.1.1 (ooofs, it's working fine) and if on the next upgrade (I'll skip 5.1.2 for sure! ;-) it happens again I'll open a bug report again, hopefuly with more time available to spend to check it. You can close this report. Btw, I understand that reproduce the problem helps a lot, but since it's my first bug report here, I'm curious: thinking about all the scripts installed on all over the world, how can you dig more into this kind of thing without having the same enviroment? ------------------------------------------------------------------------ [2006-02-01 19:34:47] [EMAIL PROTECTED] >Maybe a problem on the database code and not on XSLT (that >seems to works ok isolated)? We can't reproduce it, so you tell us. ------------------------------------------------------------------------ [2006-02-01 18:20:49] eustaquiorangel at yahoo dot com On CLI it seems that is not a problem. I run it 10 times and no error message. And using the web server seems that it's not a problem too, *** till *** (and I saw this now) I opened a script which gives me acess to our local intranet and it uses a simple database connection. Then the message is shown! I just saw that because I was testing on the CLI, on the "pure" webserver script and then I connect to get my report, and, voila, the error message is there. Maybe a problem on the database code and not on XSLT (that seems to works ok isolated)? Or maybe both? XSLT could put some junk on the memory and the database stuff just gives the error? Wow. I'm using Oracle Instant Client here. And, again, no error with any of those stuff on 5.1.1. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/36246 -- Edit this bug report at http://bugs.php.net/?id=36246&edit=1
