> It's in the docs now.
:-)
> But 85 of them are skipped... I think you forgot to create a new php.ini
> that loads Xdebug ;-)
arrrrrgggghhhhh!
ok. so, trying again with a load-xdebug-only php.ini, i.e.
% cat php.ini
[XDebugDebugger]
zend_extension_ts="/usr/local/lib/php/extensions/no-debug-zts-20060613/xdebug.so"
xdebug.auto_trace = Off
xdebug.collect_includes = On
xdebug.collect_params = Off
xdebug.collect_return = Off
xdebug.default_enable = On
xdebug.extended_info = 1
; xdebug.idekey (default: *complex*)
xdebug.manual_url = "http://www.php.net"
xdebug.show_local_vars = 0
xdebug.show_mem_delta = 0
xdebug.max_nesting_level = 100
xdebug.trace_format = 0
xdebug.trace_output_dir = "/tmp"
xdebug.trace_options = 0
;xdebug.trace_output_name = crc32
xdebug.remote_autostart = Off
xdebug.remote_enable = Off
xdebug.remote_handler = "dbgp"
xdebug.remote_host = "localhost"
xdebug.remote_mode = "req"
xdebug.remote_port = 9000
xdebug.profiler_append = 0
xdebug.profiler_enable = 0
xdebug.profiler_enable_trigger = 0
xdebug.profiler_output_dir = "/tmp"
;xdebug.profiler_output_name = "crc32"
xdebug.dump.COOKIE = ""
xdebug.dump.ENV = ""
xdebug.dump.FILES = ""
xdebug.dump.GET = ""
xdebug.dump.POST = ""
xdebug.dump.REQUEST = ""
xdebug.dump.SERVER = ""
xdebug.dump.SESSION = ""
xdebug.dump_once = On
xdebug.dump_undefined = Off
%
i see,
% sh test.sh
...
=====================================================================
Number of tests : 87 69
Tests skipped : 18 ( 20.7%) --------
Tests warned : 0 ( 0.0%) ( 0.0%)
Tests failed : 2 ( 2.3%) ( 2.9%)
Tests passed : 67 ( 77.0%) ( 97.1%)
---------------------------------------------------------------------
Time taken : 114 seconds
=====================================================================
=====================================================================
FAILED TEST SUMMARY
---------------------------------------------------------------------
Test with internal callbacks [tests/array_map.phpt]
xdebug_start_trace() without filename [tests/start_trace.phpt]
=====================================================================
hm. we're back "up" to two FAILs ...
> > so, now, the trick is find-the-conflict ... any ideas? or just hunt-n-peck?
>
> I think it's one of the variable_order settings.. but otherwise I'd
> appreciate if you could figure out which setting causes the problem.
once i understand why rm'ing php.ini content *increased* the # of
FAILs, and ensure that it's not a result of something else i've
done/not_done, i'll see what i can find ...
Received on Thu May 17 2007 - 23:23:21 BST
This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST