When does this segfault occur? Can you provide a sample script?
Also, can you try 4.2.0RC1 (see www.php.net/~derick) and see if it has been fixed?

The segfault occurs in the following code snippet (a db wrapper that we wrote for MySQL). What is odd is that this only happens on occasion: this method is called exceptionally often in our code and only breaks (in 4.1.x, not 4.0.x) once in a while and not on exceptional queries--we have, for instance, seen it break on a query that returns only one row. Anyway, here's the code:

	/** 
	* send a query to the DBMS using the dbLinkID
	* @param $dbLink - the link connection ID [INT]
	* @param $query [STRING]
	* @return the query in ORACLE format $result[FIELDNAME][ROWNUM]=value [2D HASH]
	* @access public
	*/
	function db_query($dbLink, $query){
		$res=mysql_db_query($this->dbase,$query,$dbLink);
		while($row=@mysql_fetch_array($res,MYSQL_ASSOC)){
			while(list($key,$val)=@each($row)){
				$result[$key][]=$val;
			}
			$x++;
		}
		if(!is_array($result)) $result=array();	
		return $result;
	}

Thanks for looking into this.

--jonathan

The bug still shows up in 4.2.0RC1

I just set up a separate box to test if this bug has anything to do with what version of glibc is used.

The bug is still there in the following setup:

glibc-2.2.4-19.3 (RedHat Linux 7.2)
MySQL-3.23.42-1
PHP v4.1.2 compiled as a static module for Apache 1.3.22

I was affected by the same bug, but I've found a workaround.
On linux 2.4.18, glibc 2.2.3 and MySQL 3.23.49, apache 1.3.24 with php 4.1.2 statically compiled (mysql external driver, --with-mysql=mysql_install_dir)

by explicitly indicating the link id, mysql seems to work fine. So

$conn = mysql_pconnect("host","username","pass");
mysql_select_db("db1");
$query = mysql_query("SELECT * FROM xxx")
while ($row = mysql_fetch_array($query)) do_stuff();

would randomly segfault apache, while

$conn = mysql_pconnect("host","username","pass");
mysql_select_db("db1",$conn);
$query = mysql_query("SELECT * FROM xxx",$conn)
while ($row = mysql_fetch_array($query)) do_stuff();

works without problem.

I would like to thank fcaprioli for the additional input; unfortunately, it does not resolve our problem. If you look at the code snippet that I submitted earlier, you can see that we already include the link ID in our query: i.e., "$res=mysql_db_query($this->dbase,$query,$dbLink)", where $dbLink is the link ID. So basically, we're where we were before: stuck with intermittent failures.

We are experiencing similar problems on our slack 8.0 box:

apache 1.3.26
php 4.1.2
mysql 3.23.49a

We initially saw the follow apache logs:

[Tue Jun 25 05:44:31 2002] [notice] child pid 4503 exit signal Segmentation fault (11)
[Tue Jun 25 06:11:08 2002] [notice] child pid 17668 exit signal Segmentation fault (11)

Which similar logs are generated with a pre 1.3.26 apache DOS attack script...  but since 1.3.26 is apparently patched this should not be a factor..

We also have a small built in wrapper that reports any connection failure attempts.. We have not seen any in months and since upgrading php we have started to see them more frequently... 

One note though is that all of our crashes thusfar have all occurred on 1 peticular script that processes file uploads.  This script has worked flawlessly for many months..

Sorry no backtrace so far.. I'll try and grab one..

Please try this snapshot:

http://snaps.php.net/php4-latest.tar.gz

No feedback was provided for this bug for over a month, 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".

I don't know if my uneducated comment will really contribute to the understanding of this bug, but I'll offer it up anyway:

I encountered the same problem with the exact same Apache/PHP/MySQL setup as b0nfire@fdns.net. When I changed the connection type from persistent (using mysql_pconnect) to a regular MySQL connection (using mysql_connect), the problem went away--the script worked fine and no further segfaults appeared in the http error log.

If others find the same results, then it may be safe to assume the problem is limited to persistent connections only.

Please change the status of this bug..

This bug is really bothering me, all my users are affected by this bug because it gives them empty pages :\

Here's a snippet from my errorlog:

[Mon Aug 12 12:01:16 2002] [notice] child pid 20887 exit signal Segmentation fault (11)
[Mon Aug 12 12:03:09 2002] [notice] child pid 20929 exit signal Segmentation fault (11)
[Mon Aug 12 12:03:28 2002] [notice] child pid 20938 exit signal Segmentation fault (11)
[Mon Aug 12 12:05:09 2002] [notice] child pid 20562 exit signal Segmentation fault (11)
[Mon Aug 12 12:05:18 2002] [notice] child pid 21044 exit signal Segmentation fault (11)
[Mon Aug 12 12:06:30 2002] [notice] child pid 20925 exit signal Segmentation fault (11)
[Mon Aug 12 12:07:07 2002] [notice] child pid 21078 exit signal Segmentation fault (11)
[Mon Aug 12 12:07:13 2002] [notice] child pid 21086 exit signal Segmentation fault (11)
[Mon Aug 12 12:07:17 2002] [notice] child pid 20559 exit signal Segmentation fault (11)
[Mon Aug 12 12:07:29 2002] [notice] child pid 21091 exit signal Segmentation fault (11)
[Mon Aug 12 12:07:37 2002] [notice] child pid 21094 exit signal Segmentation fault (11)
[Mon Aug 12 12:10:19 2002] [notice] child pid 21237 exit signal Segmentation fault (11)
[Mon Aug 12 12:10:26 2002] [notice] child pid 21240 exit signal Segmentation fault (11)
[Mon Aug 12 12:10:57 2002] [notice] child pid 21249 exit signal Segmentation fault (11)


Mainly using phpBB 2.0.1 on that site. Furthermore I'm using PHP version 4.2.2 on Linux 2.4.18-5, Apache/1.3.26 with MySQL 3.23.47.
See http://www.bokt.nl/klad/info.php for phpinfo().

Getting the same problems as the last poster - lots of SIGSEGVs then the apache processes seem to hang - can't get any data out of them.

hi people,

i cant get a rest .. this issue just took me weeks for now .. is there some new knowledge around about this BUG? well ist it one .. is it just bad php-code .. i am totally lost in this issue .. plz anybody gives more info and a status about this .. i touched this problem using latest version am xams(.sourgeforge.net) .. its annoying

Same problem:
PHP 4.2.3 compiled from php.net sources
Distro Red Hat 7.3
Dual Intel XEON 1.8GHz
...tons of Segmentation Faults SIG(11)... :(

Any news?
Please, contact me if you have!!!
Everyone of you!

Thank you!

This is fixed in 4.3

Hi!

I was having the same problem using MySQL 4.0.12 and PHP 4.2.2.

I figured out I should never made a symlink from /usr/lib/libmysql.so.10 to the actual file /usr/lib/libmysql.so.12 (the package required .10 but I only had .12 and I assumed the lib was pretty much stable and had similar functions than .10).

In fact, after deleting the link and downgrading the MySQL-shared-4.0.12 to MySQL-shared-3.23 as this package adds the correct libmysql.so.10, the segmentation faults stopped.

Finnaly, after a few days of zero sized reply, blank pages and apache slowness, my problem is solved...

Hope this tip helps someone.

Regards,
Raul

Sorry, I meant "libmysqlclient" instead of "libmysql" in the previous post.

Hi
The last contrib is the good one. 
Only our machines with MySQL-shared not at the same version as MySQL-client show the segmentation fault. After the upgrades, all become fine again.
Many Thanks
( apache 1.3.28 , php 4.3.2 , mysql 4.1 )