In order to know, I would need at least a GDB backtrace, and even better would be a short reproducing case to go with this. I don't have the time to debug phing.

is it something below you are looking for? Sorry to say but I'm not quite good with *unix:)

$ bashdb /usr/local/bin/phing
Bourne-Again Shell Debugger, release bash-3.1-0.08
Copyright 2002, 2003, 2004, 2006, 2007 Rocky Bernstein
This is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.

(/usr/local/bin/phing:9):
9: PHP_COMMAND="/usr/local/bin/php"
bashdb<0> next
(/usr/local/bin/phing:10):
10: export PHP_COMMAND
bashdb<1> next
(/usr/local/bin/phing:22):
22: $PHP_COMMAND -d html_errors=off -qC /usr/local/lib/php/phing.php -logger phing.listener.AnsiColorLogger "$@"
bashdb<2> next
Buildfile: /home/husen/project/fads/test/build.xml

fads4coreadmin > unittest:

[delete] Deleting directory /tests/unittests/reports
[mkdir] Created dir: /tests/unittests/reports/coverage
[coverage-setup] Setting up coverage database for 6 files
[coverage-report] Transforming coverage report

BUILD FINISHED

Total time: 2.2016 seconds

/usr/local/bin/phing: line 22: 26833 Segmentation fault $PHP_COMMAND -d html_errors=off -qC /usr/local/lib/php/phing.php -logger phing.listener.AnsiColorLogger "$@"
(/usr/bin/bashdb:288):
288:
bashdb<3> bt
->0 in file /usr/bin/bashdb' at line 288 ##1 main() called from file/usr/bin/bashdb' at line 0
bashdb<4> q

No, I need a gdb backtrace. See: http://bugs.php.net/bugs-generating-backtrace.php (probably the bit for "command line" under "If you can't get a core file:"

Requested feedback not provided.