Am So, den 13.03.2005 schrieb a a um 22:29:
I'm having a similar problem, which is a segmentation fault in the PHP code. It should be in your error_log if that is the case. Unfortunately, I'm still trying to solve the problem, so if you are having the same problem, I don't have a solution yet.
thank you for the reply i was pulling my hair out. i figured it was a php problem cos the php code is not being served when i open the file in the browser ... i have started at the beginning with the apache config but couldnt find the problem there either
I am sure there is no PHP problem as I have phpMyAdmin running on an FC3 system without any problem.
C'mon Alexander, one working system is hardly conclusive evidence :-). Speaking only for myself, I believe my problem is that for some reason PHP when (and only when) accessed via apache is using the wrong mysqli API. I have a very small script that crashes and have done a backtrace and put print statements in the code. It is a PHP problem, which is not to say that it is a bug in their code. Mostly likely it is either a problem with my system or a bug in the PHP configuration program.
I haven't done a backtrace on the phpMyAdmin, so it might not even be the same problem, but I'm pretty sure that it is.
I've posted this in the php.general newsgroup, but if anyone here can tell me why the mysql API version is 3.23.58 when I do a phpinfo() from a browser, but is 4.1.10a when I do a command line call to "php -i", I would love to know. I'm assuming that is my real problem (the script works in the latter case and crashes and burns in the former).
