ID: 27990 Updated by: [EMAIL PROTECTED] Reported By: csaba at alum dot mit dot edu -Status: Feedback +Status: No Feedback Bug Type: SQLite related Operating System: Win 2K PHP Version: 5CVS-2004-05-03 (dev) New Comment:
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". Previous Comments: ------------------------------------------------------------------------ [2004-07-10 15:09:51] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip ------------------------------------------------------------------------ [2004-05-03 23:46:34] csaba at alum dot mit dot edu The good news is that the behaviour is markedly better. This time instead of failing disastrously every other time, it only fails petulantly every third time. I tested this both as you asked with the CLI version and also running PHP as a module. With the CLI version, testing on my small three file directory, I got behaviour as expected: I got warnings on files SQLITE didn't like and when I supressed them with the @ in front of sqlite_open, the result was that I got a report of the single sqlite database file in the directory. Very nice. Thus encouraged, I went back to the original scenario and ran the same file through a browser. Two out of three times, I get the same behaviour as above. The third time around, however, I get the following variable error message: Fatal error: Unknown function: 8�() in C:\Morph\phpDev\php.php on line 28 There are two things I'd like to mention. The first is that the "text" between the ': ' and ' in' seems to always be garbage characters, and always different For the second, I have to clear my throat a bit and mutter something about Heisenberg's uncertainty principle. The only thing on that line 28 the error message is referring to is the function sqlite_escape_string. (Ahem. Whenever I test, I submit the PHP code through a preprocessor that logs the submission. This has been very stable. The submission is stuffed into a temporary file and after the logging is done, the browser gets back a header("Location: ...") to the temporary file. (The directory that I was doing this sqlite testing on is in a separate tree)). Therefore, I also created a separate file with just the code I submitted (surrounded in appropriate tags). The results there were not so encouraging. Apache is still crashing, and PHP complains about trivial things like it can't find this or that variable, always in the dirList function on different lines. Let me know if you need more info. The good news is that I deal with this by opening up all the files I find and scanning their header to see if they're SQLite files, and this is working fine for me. Why can't SQLite do that? So, although this problem isn't affecting me cause of my workaround, I figured you'd like to know the current status of it on my machine. Csaba Gabor ------------------------------------------------------------------------ [2004-04-29 15:16:53] [EMAIL PROTECTED] No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2004-04-22 23:30:25] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip What you're trying to do will probably end in tears; libsqlite has a tendency to clobber files that are not valid sqlite databases (this is not a PHP problem). It is possible that PHP is overly sensitive to such a problem, so could you please try to reproduce this using the CLI version of PHP? Use a snapshot from the link above. ------------------------------------------------------------------------ [2004-04-22 23:10:32] csaba at alum dot mit dot edu I have tested this with the latest release (April 22 RC 2 beta), and it still crashes Apache. However, I can be a bit more specific about the symptoms. I tested on a directory with a small sqlite database log.db (48K) and a log.php file (6K). Both files were required to produce the crashing effect. If I ran the code below (with or without an @ in front of the sqlite_open) the first time I would get a warning about: database disk image is malformed ... (if the @ was not present, as with the code below). The NEXT Time I invoked the same code is when the Apache would give me the error message about restarting (and sometimes die). This happens regardless of whether I remove log.php from the directory tree before running the test the second time. Csaba Gabor ------------------------------------------------------------------------ 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/27990 -- Edit this bug report at http://bugs.php.net/?id=27990&edit=1
