Bug 248188 - *** stack smashing detected ***: /usr/bin/php-cgi terminated
Summary: *** stack smashing detected ***: /usr/bin/php-cgi terminated
Alias: None
Product: Fedora
Classification: Fedora
Component: php   
(Show other bugs)
Version: 7
Hardware: All Linux
Target Milestone: ---
Assignee: Joe Orton
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-13 19:33 UTC by Itamar Reis Peixoto
Modified: 2008-06-17 01:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-17 01:52:34 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Itamar Reis Peixoto 2007-07-13 19:33:06 UTC
Description of problem:
I am running php as fastcgi in lighttpd, and my php is crashing causing lighttpd
 stop to server pages.

also when I run lighttpd using the gdb I see the smash stack message on gdb
console but the lighttpd continue to server pages, but if running lighttpd
without gdb the lighttpd stop serving pages if php crashes with stack smash

Version-Release number of selected component (if applicable):


Comment 1 Joe Orton 2007-07-16 05:10:22 UTC
Can you get a core dump?

1) ensure lighttpd is starting with "ulimit -c unlimited"
2) ensure core dumps go somewhere useful

  # sysctl kernel.core_pattern=/var/core/core.%e.%p
  # mkdir /var/core

Comment 2 Itamar Reis Peixoto 2007-07-18 02:08:12 UTC
lighttpd is now working fine after started with "ulimit -c unlimited" 

(3 day's working fine without stopping to server pages)

I can ignore this because the lighttpd is not stopping to server pages.

but I am still able to see stack smash messages in /var/log/messages, also 
there are no core files created in /var/core

[root@server log]# cat messages|grep stack
Jul 15 16:25:46 server php-cgi: *** stack smashing detected ***: /usr/bin/php-
cgi terminated
Jul 16 02:22:06 server php-cgi: *** stack smashing detected ***: /usr/bin/php-
cgi terminated
Jul 16 18:29:41 server php-cgi: *** stack smashing detected ***: /usr/bin/php-
cgi terminated
Jul 17 10:57:51 server php-cgi: *** stack smashing detected ***: /usr/bin/php-
cgi terminated

Comment 3 Bug Zapper 2008-05-14 13:32:30 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2008-06-17 01:52:32 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.