xdebug.trace_format=1 ignored

xdebug.trace_format=1 ignored

I'm trying to find a memory leak in my PHP code using
http://derickrethans.nl/xdebug-and-tracing-memory-usage.html It appears
that xdebug.trace_format=1 is being ignored and I don't know why.
I'm running the PHP script from the command-line on the Mac.
/etc/php.ini has:
[xdebug]
; xdebug.idekey="macgdbp"
xdebug.default_enable=1
; xdebug.remote_enable=1
; xdebug.remote_handler=dbgp
; xdebug.remote_host=localhost
; xdebug.remote_port=9000
; xdebug.remote_autostart=1
xdebug.profiler_append=1
xdebug.profiler_enable=1
; xdebug.profiler_enable_trigger=1
xdebug.profiler_output_name=cachegrind.out.%s
xdebug.profiler_output_dir=/tmp/xdebug
xdebug.show_mem_delta=1
xdebug.trace_format=1
xdebug.trace_enable_trigger = 1
xdebug.auto_trace = On
phpinfo() says, among many other things:
PHP Version => 5.3.26
with Xdebug v2.2.3, Copyright (c) 2002-2013, by Derick Rethans
xdebug
xdebug support => enabled
Version => 2.2.3
IDE Key => jernst
Supported protocols => Revision
DBGp - Common DeBuGger Protocol => $Revision: 1.145 $
Directive => Local Value => Master Value
xdebug.auto_trace => On => On
xdebug.cli_color => 0 => 0
xdebug.collect_assignments => Off => Off
xdebug.collect_includes => On => On
xdebug.collect_params => 0 => 0
xdebug.collect_return => Off => Off
xdebug.collect_vars => Off => Off
xdebug.coverage_enable => On => On
xdebug.default_enable => On => On
xdebug.dump.COOKIE => no value => no value
xdebug.dump.ENV => no value => no value
xdebug.dump.FILES => no value => no value
xdebug.dump.GET => no value => no value
xdebug.dump.POST => no value => no value
xdebug.dump.REQUEST => no value => no value
xdebug.dump.SERVER => no value => no value
xdebug.dump.SESSION => no value => no value
xdebug.dump_globals => On => On
xdebug.dump_once => On => On
xdebug.dump_undefined => Off => Off
xdebug.extended_info => On => On
xdebug.file_link_format => no value => no value
xdebug.idekey => no value => no value
xdebug.max_nesting_level => 100 => 100
xdebug.overload_var_dump => On => On
xdebug.profiler_aggregate => Off => Off
xdebug.profiler_append => On => On
xdebug.profiler_enable => On => On
xdebug.profiler_enable_trigger => Off => Off
xdebug.profiler_output_dir => /tmp/xdebug => /tmp/xdebug
xdebug.profiler_output_name => cachegrind.out.%s => cachegrind.out.%s
xdebug.remote_autostart => Off => Off
xdebug.remote_connect_back => Off => Off
xdebug.remote_cookie_expire_time => 3600 => 3600
xdebug.remote_enable => Off => Off
xdebug.remote_handler => dbgp => dbgp
xdebug.remote_host => localhost => localhost
xdebug.remote_log => no value => no value
xdebug.remote_mode => req => req
xdebug.remote_port => 9000 => 9000
xdebug.scream => Off => Off
xdebug.show_exception_trace => Off => Off
xdebug.show_local_vars => Off => Off
xdebug.show_mem_delta => On => On
xdebug.trace_enable_trigger => On => On
xdebug.trace_format => 1 => 1
xdebug.trace_options => 0 => 0
xdebug.trace_output_dir => /var/tmp/ => /var/tmp/
xdebug.trace_output_name => trace.%c => trace.%c
xdebug.var_display_max_children => 128 => 128
xdebug.var_display_max_data => 512 => 512
xdebug.var_display_max_depth => 3 => 3
An output file is generated at /tmp/xdebug/cachegrind.out.-something but
it starts with
==== NEW PROFILING FILE ==============================================
version: 1
creator: xdebug 2.2.3
cmd: something
part: 1
positions: line
instead of version 2 of the trace format that I was expecting. So I can't
run the memory analysis script on it. Suggestions?