views:

205

answers:

3

I know (PHP's) var_dump is supposed to be "human readable" and all, but analyzing large objects is just a pain in the neck. I am struggling to make sense of a few of the large objects that are being passed around in a script that we are running. (I know that using xdebug with and IDE is a good idea, but I have not been able to get xdebug to run on this project for some reason - several days lost, ugh).

Any ideas on how I can easily digest the contents of a really big var_dump? Any ideas are welcome... Although I am hoping that there is something similar to Thomas Frank's JSON tool (where you just put some code in and it gives a nice graphical representation).

A: 

Interesting question. I'd make my own var_dump() equivalent based on some recursive function. With some parameters (such as nesting level, certain element name, etc) to pass it could be quite useful I think.

Col. Shrapnel
+6  A: 

I'd just use dBug.

Billy ONeal
Oh that's great!
Col. Shrapnel
I was going to suggest dBug too. I include it in every project I make now, I can't imagine working without it.
Arms
Thanks for sharing this. dBug looks really nice var_dump replacement. I must say that FirePHP seems a little more convenient since it doesn't muck up the entire webpage you are trying to debug. Cheers!
sdek
+3  A: 

You could take a look at FirePHP. It enables you to write information to the firebug-console. If you write an array or object to the log and hover with your mouse over it, you get a nice presentation of the contents of that array. Here is a screenshot of a simple example.

murze
Looks like I already had FirePHP integrated in my project, so I used it. Very useful. It does exactly what I was looking for.
sdek