Your message dated Wed, 27 Apr 2011 10:28:24 +0200
with message-id <[email protected]>
and subject line Closing segfaults (and some other minor bugs) for version
older than squeeze (5.3.3)
has caused the Debian Bug report #493045,
regarding Segmentation Fault in cron console PHP Job
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
493045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493045
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: php5
Version: 5.2.6-2
Hi there,
exactly since we upgraded to this package we get intermittent
Segmentation Faults from two cron jobs each running a php skript every 5
minutes.
During the last 7 days this happened 20 times. The scripts have not
changed for months now and they ran without any problem at all.
One example (content of the cron status mail):
/bin/sh: line 1: 13954 Segmentation fault /sbin/mailbox_watcher
>>/var/log/mailbox_watcher.log
This mailbox watcher does some checks on a mysql DB and synchronizes
possible changes with the filesystem on the harddrive. Nothing special
and it seems that most of the time (99%) everything runs fine. What is
also confirmed is that it does not depend on the code cases that are
executed, this means it does not depend whether the check skript
returns without having to synchronize or after doing so.
I am simply not able to reproduce it. Although it keeps happening.
Any thoughts on that? If you see any procedure, logs, etc I could try to narrow
the problem down with, pls let me know.
One word about the complexity of the two skripts. They are totally
different. The one is just a "dirty" procedural code, the other is
more object oriented with a class defined.
See the first lines of this skript below:
> #!/usr/bin/php5
> <?php
>
> define('_UNDEFINED',0);
> define('_FATAL',1);
> define('_CRITICAL',2);
> define('_WARNING',3);
> define('_INFO',4);
>
> define('_EXITTHRESHOLD',2);
>
> define('_CRLF',"\n");
>
> class checkAuthDB {
>
> var $ident;
> var $conf;
> var $dblinks;
> var $lastrun;
> var $user;
> var $logIsOpen;
> var $logfp;
>
> function __construct($ident) {
>
> (...)
Ok, and here the first lines of the mailbox_watcher
> #!/usr/bin/php5
> <?php
>
> // initialising some variables...
>
> // mysql connect information (if needed)
> $db_host="...";
> $db_user="...";
> $db_password="...";
> $db_name="...";
>
> $output_init=false;
>
> // registering needed functions...
>
> function insdate() {
>
> (...)
Thanks in advance for all your efforts!!
--
Regards,
Timo Kirst
--- End Message ---
--- Begin Message ---
Version: 5.3.3-7
Hi,
since lenny is oldstable it will not get any updates now (except
security)[1], I am closing all segfault bugs filled against php5 in
lenny. (This is kind of saying that we don't care much about php5 in
lenny anymore).
If you believe the bug is still there, please provide evidence[2] and
a (preferably complete) test case with up-to-date squeeze (and/or
testing or unstable) version of php5 and reopen the bug.
O.
1. http://wiki.debian.org/PHP#Notes_on_PHP_and_security
2. Install php5-dbg and provide backtrace:
http://bugs.php.net/bugs-generating-backtrace.php
--
Ondřej Surý <[email protected]>
--- End Message ---
