runcronjobs.php - Segmentation fault

Author Message

Michael Zeidler

Thursday 30 September 2004 12:04:33 am

Hello,

i have runcronjob.php in revision 8358 and everytime i start this it fails at the end with a segmentation fault which produces a core dump file in the ezroot directory. I also commented out the usual envoked scripts (./cronjobs/*) in ./settings/cronjob.ini. Then i added a ./cronjobs/test_dummy.php and also added it in the cronjob.ini. After running ./runcronjob.php a segmentation fault occurs again. So runcronjob.php itself must be the bugger.
Any ideas?

-------------------------------------------------------------------------------------------
join #ezpublish on irc.freenode.org

Jan Borsodi

Thursday 30 September 2004 12:15:20 am

eZ publish in itself cannot segfault, only PHP can do that.
If this happens I would guess there is some issues with your PHP version.
What is your PHP version?

Does the <i>runcronjobs.php</i> from 3.4 still work or is the problem only in trunk (rev. 8358)?
Note: I tried runcronjobs.php with that revision and didn't get a segfault.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Michael Zeidler

Thursday 30 September 2004 2:04:46 am

Hallo Amos,
of course this is only php related. I also realized that no other complaints where droped about it here in this forum.
It also cores down with the offcial 3.4.1 version, but no wonder look at this:

# php -v
PHP 4.3.4 (cli) (built: Jul 13 2004 20:39:44)
Copyright (c) 1997-2003 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2003 Zend Technologies
    with Turck MMCache v2.4.6, Copyright (c) 2002-2003 TurckSoft, St. Petersburg, by Dmitry Stogov
    with DBG v2.11.5, (C) 2000,2001,2002, by Dmitri Dmitrienko
zsh: segmentation fault (core dumped)  php -v

So I configured my php without dbg support and my problems vanished ;)

I had a broken php-dbg installation. You should delete this thread.
Thanks anyway.

mike

-------------------------------------------------------------------------------------------
join #ezpublish on irc.freenode.org

Jan Borsodi

Thursday 30 September 2004 6:44:20 am

Btw. If you want a PHP debugger/profiler I can recommend XDebug.
http://xdebug.org/
The latest version works pretty well with eZ publish.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 31 2025 11:39:45
Script start
Timing: Jan 31 2025 11:39:45
Module start 'layout'
Timing: Jan 31 2025 11:39:45
Module start 'content'
Timing: Jan 31 2025 11:39:45
Module end 'content'
Timing: Jan 31 2025 11:39:45
Script end

Main resources:

Total runtime0.0216 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0088 588.1328151.2109
Module start 'layout' 0.00880.0045 739.343836.6484
Module start 'content' 0.01330.0065 775.992294.2500
Module end 'content' 0.01980.0018 870.242233.9922
Script end 0.0216  904.2344 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002712.5688140.0002
Check MTime0.00125.7033140.0001
Mysql Total
Database connection0.00073.287110.0007
Mysqli_queries0.006731.231730.0022
Looping result0.00000.088310.0000
Template Total0.00136.010.0013
Template load0.00094.314710.0009
Template processing0.00041.624810.0004
Override
Cache load0.00062.879810.0006
General
dbfile0.00156.889980.0002
String conversion0.00000.055240.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs