PHP 4.0 Bug #8938 Updated: Segfaults

ID: 8938 Updated by: sniper Reported By: cecot@dirbg.com Old-Status: Feedback Status: Closed Bug Type: Reproduceable crash Assigned To: Comments: No feedback. If this happens with soon to be released PHP 4.0.5 too, reopen this bug report. --Jani Previous Comments: --------------------------------------------------------------------------- [2001-03-04 15:58:45] sniper@php.net Please generate a gdb backtrace of the crashes. And use the latest CVS snapshot and configure it using --enable-debug also in the configure line. --Jani --------------------------------------------------------------------------- [2001-02-06 06:21:36] cecot@dirbg.com sorry for the double report, but when I restarted the apache some of the children died with segmentation fault --------------------------------------------------------------------------- [2001-02-06 06:18:41] cecot@dirbg.com at about 2001-02-05 19:00 EET I got the CVS again and my observation is that there are no Segmentation faults for more than 15 hours, but there is still a lot of HTML code in my error.log file, if it helps --------------------------------------------------------------------------- [2001-02-02 07:37:36] cecot@dirbg.com the bug is still there. 1. I get from CVS (today) not from snaps does it matter ?? 2. in my debian distribution i have /usr/sbin/apache and /usr/sbin/apache.dbg, i made /usr/sbin writable by www-data (the apache user) both the apache and apache.dbg didn't make core file (the php from the CVS was compiled with --enable-debug=on). 3. I tried gdb /usr/sbin/apache and run -X. when I access any page with a browser nothing was seen in the browser neighter in gdb. the same with gdb /usr/sbin/apache.dbg (probaly i didn't give it enough time to start or I did something wrong, give some more inforamtion on how to do it) --------------------------------------------------------------------------- [2001-02-01 20:06:54] sniper@php.net Can you try again with today's snapshot? And to get a decent gdb backtrace configure with --enable-debug and do following: # gdb /opt/www/bin/httpd (gdb) run -X And then access the page which causes the crash and if it crashes: (gdb) bt full and then cut'n'paste the output and add it into this bug report. --Jani --------------------------------------------------------------------------- The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online. ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=8938&edit=2