ID: 41194 User updated by: bugs dot php at anonymousmail dot net Reported By: bugs dot php at anonymousmail dot net -Status: Bogus +Status: Open Bug Type: Reproducible crash Operating System: Windows XP Professional x64 Edit PHP Version: 5.2.1 New Comment:
>Crash? What crash are you talking about? I changed the bug status back to open. This is a real crash. Read on to see why. This crash (a crash according to Windows) occurred on my system when I installed all extensions like I explained in my original post and is caused by simply typing "php" at the Windows command prompt. This crash was the source of the dump which I already posted, right below the following text: "Here is the report from the php CLI crashing from typing "php" at the command prompt." The person from bug #39781 had similar errors to those that I received. They got the error message, "There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor." This error probably has something to do with installing extensions. As I explained in my first post, I got that same error message. They also had this error message, "CGI / FastCGI has encountered a problem and needs to close." My error message was identical except mine said php.exe because that was what I had executed. This message is different than a warning message. All I did was type "php" at the command prompt and hit enter. Then, windows pops up a error message saying the above. I am then promptly returned to the command prompt after I dismiss the error message. With a warning, I would still be inside PHP. I think one of the extensions is actually making PHP crash. I have installed some extensions and gotten warnings in Apache, but PHP still ran the script <?php phpinfp(); ?> However, when I had installed all the extensions, PHP wouldn't execute that script. I seriously do believe that one of the extensions is making PHP crash for real. This is what I already posted from my Apache log file: [error] [client 127.0.0.1] PHP Fatal error: require_once() [<a href='function.require'>function.require</a>]: Failed opening required 'SAM/php_sam.php' (include_path='.;C:\\php5\\pear') in sam_factory on line 1, referer: http://localhost/ Notice it says, "PHP Fatal error", a.k.a. crash. And it also crashed when I ran "php" from the command line. (Also, pear and php wasn't installed at the location it gave in the include_path.) So, it is crashing in the Apache module and also from php.exe on the command line. Over the years, I have seen lots of different programs crash. It looks just like a crash to me. If I do not install all extensions, PHP runs great, which makes me conclude that an extension is causing the crash. I am running the 64bit version of Windows XP Pro. I don't know if that has anything to do with PHP crashing. I have noticed that quite a lot of older programs don't like to run on this OS. Maybe this is the problem with whatever extension might be causing the crash. If you want, I will be glad to provide any more information! >Startup warnings are no crashes and you should start reading the docs >before installing anything. >Not PHP problem. "RTFM", I understand that. However, for example, I am looking at this from the perspective of someone who buys a book about blogging, etc. The book briefly covers how to install Apache, PHP and MySql. Then continues on with installing blog software (written in PHP), etc. This person would be following step-by-step what the book says. Sometimes problems occur which are unforeseen by the books author. This person probably isn't going to know about "RTFM" or even where to find it. I was this person several years ago! Basically, my solution to all this is to possibly offer a 'simple' and 'advanced' selection on the installer. The simple selection will explain about "RTFM", install the docs and offer to create shortcuts to them. Most importantly, it will explain about the caveats of installing extensions with unmet dependencies. Granted, it does say something about this on the area where you can select extensions. However, it doesn't explain much about it or explain why, etc. The person from bug #39781 didn't even have the luxury of having a book to reference. Previous Comments: ------------------------------------------------------------------------ [2007-04-26 22:54:44] [EMAIL PROTECTED] >My point was, if someone wants to install php and they don't know >about this stuff, then they will be UNABLE to use php! These are just warnings and they say "you did not read the docs, go now and read them". >For the longest time I tried to get php to work on my computer. >I gave up many times. Well, you should really start with the docs. >..they usually don't expect to maximize the likelihood that it >will crash for unknown (to them) reasons! Crash? What crash are you talking about? >You can't expect everyone that wishes to learn and use php to be >knowledgeable about dependencies, etc. They just want to LEARN how to >use php, which they can't do if they can't successfully install php! Huh? Dependencies? All these dependencies are described in the docs and we do expect everyone to be able to read. >This is a real bug, because if you install all the extensions, it >crashes and it's reproducible. >If it crashes AND it's reproducible, is that not a bug??? Startup warnings are no crashes and you should start reading the docs before installing anything. Not PHP problem. ------------------------------------------------------------------------ [2007-04-26 22:03:43] bugs dot php at anonymousmail dot net Yes, it is apparent that these extensions require third party libraries. Which is exactly why I posted this bug report in the first place. My point was, if someone wants to install php and they don't know about this stuff, then they will be UNABLE to use php! I know this from past experience. For the longest time I tried to get php to work on my computer. I gave up many times. Finally, I figured out what was happening with the extensions! Then I took a great deal of time to document what was happening so you could see exactly what I was talking about. When someone installs software on their computer, they usually want to install everything to maximize the potential of the software. When they do this, they usually don't expect to maximize the likelihood that it will crash for unknown (to them) reasons! You can't expect everyone that wishes to learn and use php to be knowledgeable about dependencies, etc. They just want to LEARN how to use php, which they can't do if they can't successfully install php! You can call this a bogus bug if you want, but it apparently is a real issue for some users. This is a real bug, because if you install all the extensions, it crashes and it's reproducible. If it crashes AND it's reproducible, is that not a bug??? ------------------------------------------------------------------------ [2007-04-26 08:59:52] [EMAIL PROTECTED] All these extensions require thirtd party libraris which are apparently missing in your system. ------------------------------------------------------------------------ [2007-04-26 00:25:45] bugs dot php at anonymousmail dot net One small thing I noticed while looking at phpinfo is that the internal value of "include_path" is ".;C:\php5\pear". I installed pear, but the installer didn't change include_path. ------------------------------------------------------------------------ [2007-04-25 23:57:51] bugs dot php at anonymousmail dot net In the FileAlyzer output, it says: File: C:\Programs\php5\ext\php_netools.dll This is where I had originally installed php. I completely uninstalled php and reinstalled it to the default location thinking it would help, but it didn't. ------------------------------------------------------------------------ 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/41194 -- Edit this bug report at http://bugs.php.net/?id=41194&edit=1
