ID: 36246 User updated by: eustaquiorangel at yahoo dot com Reported By: eustaquiorangel at yahoo dot com -Status: Feedback +Status: Open Bug Type: XSLT related Operating System: Linux, Slackware 10.2 (current) PHP Version: 5.1.2 New Comment:
> 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? Previous Comments: ------------------------------------------------------------------------ [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. ------------------------------------------------------------------------ [2006-02-01 17:30:34] [EMAIL PROTECTED] Can you get a backtrace? It's working fine for me on both win and linux boxes. does it crash under cli too? ------------------------------------------------------------------------ [2006-02-01 17:24:14] eustaquiorangel at yahoo dot com No way to avoid it with 5.1.1 +. :-( I downloaded the snapshot you told me, installed (phpversion() gives me "5.1.3-dev") and when running the sample, it shows me again the error_log message: *** glibc detected *** double free or corruption (fasttop): 0x082392a0 *** [Wed Feb 01 14:10:20 2006] [notice] child pid 11636 exit signal Aborted (6) I'm checking http://www.php.net/ChangeLog-5.php and seems that on the Windows version there were some changes: # Updated to libxml2-2.6.22 and libxslt-1.1.15 in the win32 bundle. (Rob) It's exactly the same versions I'm running here on Linux. And there were some little stuff like # Added constants for libxslt and libexslt versions: LIBXSLT_VERSION, LIBXSLT_DOTTED_VERSION, LIBEXSLT_VERSION and LIBEXSLT_DOTTED_VERSION. (Pierre) that would not affect this way the behaviour. I did some diffs with the ext/xsl 5.1.1 and 5.1.2 files but didn't find some relevant changes, just comment changes. Now I downgraded again to 5.1.1 and it's working fine again, no errors. Could you test the code on a Linux computer? ------------------------------------------------------------------------ [2006-02-01 16:19:43] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5.1-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.1-win32-latest.zip Works fine here. ------------------------------------------------------------------------ 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
