Pimping Xdebug stack traces
I've always been annoyed by the way how Xdebug's stack traces looked liked. So I spend some time on making them look better. I will show the differences according to the following script:
<?php
ini_set('xdebug.show_local_vars', 'on');
ini_set('xdebug.dump_globals', 'on');
ini_set('xdebug.dump.GET', '*');
ini_set('xdebug.collect_params', 'on');
ini_set('xdebug.var_display_max_depth', 2);
function foo( $a )
{
for ($i = 1; $i < $a['foo']; $i++)
{
}
}
set_time_limit(1);
$c = new stdClass;
$c->bar = 100;
$c->foo = "12";
$a = array(
42 => false,
'foo' => 912125235,
0 => null,
3.141592654,
"testing",
array(),
$c, new stdClass,
fopen( '/etc/passwd', 'r' )
);
foo( $a, 42, null, false, "testing",
$c, fopen( '/etc/passwd', 'r' ) );
?>
Old:
New:
The code for this will make it into CVS soonish.
Comments
Nice work, will make it a lot more enjoyable to work with xdebug with the new UI :-)
that's much better!
Great, looks much better than a patch I was thinking to submit but I never finished ;)
Life Line
I've just finished reading Tim Peake's autobiography "Limitless".
No longer construction
I walked 2.2km in 25m25s
Confirmed a chocolate shop
Updated a company office and a cafe
I walked 6.6km in 1h11m59s
I walked 8.4km in 1h38m25s
Only test with 8.2 and later on master with Xdebug CI
Merge branch 'xdebug_3_5'
Remove expliciy path from Xdebug CI
I walked 9.6km in 1h38m09s
If you're wondering why the @Xdebug issue tracker is unavailable, I can conclusively say that it's another bout of LLM scrapers.
I walked 9.9km in 1h41m14s
I walked 1.3km in 14m45s
Created 18 benches and a grave; Updated 3 benches, a tree, and a waste_basket
I walked 6.1km in 3h9m07s
Updated a vacant business
Updated a bar
I walked 1.6km in 18m00s
Updated a pub
I walked 3.4km in 54m56s
I walked 1.9km in 23m48s
Updated a pub
I walked 3.4km in 22m41s
Updated a restaurant


Shortlink
This article has a short URL available: https://drck.me/p-xdebug-st-4xw