Warum wirft PHP nach "mysql_connect" oder bei "mysql_close" "Segmentation fault (11)"?

This could be a hardware problem or an Apache/PHP configuration problem. I've usually seen Signal 11 with memory problems. Look at your configs to make sure that the PHP memory limit isn't higher than the Apache memory limit or similar.

It sounds like your php_mod is crashing mid-program, so Apache is just tossing the php file at you with a non-html content-type header, which makes your browser treat it as a download. That's just a guess, though. You need to gather some more information.

Add some error_log() calls to your PHP program so that you can isolate when the crash actually occurs in your code. If that doesn't help narrow it down, set up Apache to create a core dump and use gdb to figure out where the segfault starts. My bet is mod_php.so.

You say it's all up and running and that simple files are showing up okay. But then some files are prompting you to save the PHP file. This means you'll have to look at the code of those pages where it's breaking and asking you to save.

It's more than likely you have a line in the code that is killing the server or just making it give up parsing the PHP.

This could be a particular extension that's being used by that page or it could be another killbot function that hobbles the server into just sitting there with its arms crossed.

Your error logs show that the last thing to happen before it shoves the save dialog in your face is a connect to the database. Follow the code back to that and make sure that's solid before moving onto the next possible troubleshooting breadcrumb that may or may not arise.

Since you can see the file with no problem on another set up, in this case easyPHP, the problem is very much on the XAMPP set up and a configuration that is being tripped up by the code.

Smells like your mysql install. Is mysql running as a service? Does your root account really have no password? What mysql extensions are loaded in php.ini? There's a php_mssql.dll which can easily be mistaken for php_msql.dll, but I'm fairly certain the php_mssql.dll is for windows only.

Have you edited your php.ini /opt/lampp/php/php.ini? These may help with debugging:

error_reporting = E_ALL & ~E_NOTICE display_errors = On display_startup_errors = On ;but you'll want to turn this off soon ;) mysql.trace_mode = On 

Also worth looking at, the port number used. Is $MYSQL_TCP_PORT set? How about the mysql-tcp entry in /etc/services?

Update: Have you tried checking the return value of the connect function? I'm wondering if you example is too minimal. Try making your test look like this:

<?php $db = mysql_connect("localhost","root","myrootpassword"); if (!$db) { die('Could not connect: ' . mysql_error()); } else { $result = mysql_query("show databases"); print " <h1>Test executed from ". $_SERVER['SCRIPT_NAME']. "</h1> \n"; print "Script name: ". $_SERVER['SCRIPT_FILENAME'] ." <hr>\n"; while ($line = mysql_fetch_array($result)) { print "$line[0]<br>\n"; } } mysql_close($db); ?> 

This example ensure you send something back that looks like HTML whether your script fails or not. I was able to reproduce your symptoms with no root password set, so it's apparently not only good practice, but it's required to be non-empty.

I was able to turn your problem into a a solution by

1. Setting the root password
2. returning something from the script on connect

Instead of passing in "" as the root password, if it really is nothing, try using mysql.default_password as the password. The default value for mysql.default_password is NULL.

Ich habe genau den gleichen Fehler festgestellt. Stellen Sie sicher, dass die mysql-Benutzerrechte richtig eingestellt sind.

Melden Sie sich in der Befehlszeile an und bestätigen Sie, dass Sie sich anmelden können, wechseln Sie zu der betreffenden Datenbank und sehen Sie Tabellen und Datensätze. Melden Sie sich einfach mit dem Befehl "mysql -u user -p" an und lösen Sie einige Abfragen aus.