php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #10117 mysql_pconnect() can cause segmentation fault
Submitted: 2001-04-02 13:00 UTC Modified: 2001-06-04 04:28 UTC
From: jules at acris dot co dot uk Assigned:
Status: Not a bug Package: MySQL related
PHP Version: 4.0.4pl1 OS: Linux 2.2.14
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: jules at acris dot co dot uk
New email:
PHP Version: OS:

 

 [2001-04-02 13:00 UTC] jules at acris dot co dot uk
In the process of setting up a new site on my server, I set up a MySQL database for it and a new MySQL user, but neglected to perform a 'mysqladmin reload' to process the new user's password.  The call to mysql_pconnect() failed and the page in question did not work, but subsequent calls to the same page produced a segmentation fault in the httpd error log.

The problem did not clear up until I killed the server and restarted it, but now I cannot reproduce it.

Other software details:

[root@fddth03-157-31 panet_demo]# httpd -V
Server version: Apache/1.3.6 (Unix)
Server built:   Mar  7 2000 17:30:02
Server's Module Magic Number: 19990320:0
Server compiled with....
 -D EAPI
 -D BIG_SECURITY_HOLE
 -D HAVE_MMAP
 -D HAVE_SHMGET
 -D USE_SHMGET_SCOREBOARD
 -D USE_MMAP_FILES
 -D USE_FCNTL_SERIALIZED_ACCEPT
 -D HTTPD_ROOT="/etc/httpd"
 -D SUEXEC_BIN="/usr/bin/suexec"
 -D SHARED_CORE_DIR="/usr/lib/apache"
 -D DEFAULT_PIDLOG="/var/run/httpd.pid"
 -D DEFAULT_SCOREBOARD="/var/run/httpd.scoreboard"
 -D DEFAULT_LOCKFILE="/var/run/httpd.lock"
 -D DEFAULT_XFERLOG="/var/log/httpd/access_log"
 -D DEFAULT_ERRORLOG="/var/log/httpd/error_log"
 -D TYPES_CONFIG_FILE="conf/mime.types"
 -D SERVER_CONFIG_FILE="conf/httpd.conf"
 -D ACCESS_CONFIG_FILE="conf/access.conf"
 -D RESOURCE_CONFIG_FILE="conf/srm.conf"
Compiled-in modules:
  http_core.c
  mod_mmap_static.c
  mod_env.c
  mod_define.c
  mod_log_config.c
  mod_log_agent.c
  mod_log_referer.c
  mod_mime_magic.c
  mod_mime.c
  mod_negotiation.c
  mod_status.c
  mod_info.c
  mod_include.c
  mod_autoindex.c
  mod_dir.c
  mod_cgi.c
  mod_asis.c
  mod_imap.c
  mod_actions.c
  mod_speling.c
  mod_userdir.c
  mod_proxy.c
  mod_alias.c
  mod_rewrite.c
  mod_access.c
  mod_auth.c
  mod_auth_anon.c
  mod_auth_db.c
  mod_digest.c
  mod_cern_meta.c
  mod_expires.c
  mod_headers.c
  mod_usertrack.c
  mod_example.c
  mod_unique_id.c
  mod_so.c
  mod_setenvif.c
  mod_ssl.c
  mod_perl.c
  mod_auth_pam.c

PHP was configured with the MySQL provided library

MySQL 3.23.33

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-06-02 22:27 UTC] sniper@php.net
User error.

 [2001-06-04 04:28 UTC] jules at acris dot co dot uk
In what way is this a user error?  I agree that the problem was caused by an error I made, but I maintain that the segmentation faults caused by this are a symptom of a bug: PHP should not segfault and cause apache to produce invalid results for a request.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Fri Apr 19 10:01:28 2024 UTC