Hello, guest. We have noticed that you are not registered at this bug tracker. Your experience will be greatly enhanced if you log in. To do so, you first must register by clicking on the Register tab at the top. If you are already registered, you can login at the Login tab.
Syndicate Syndicate Listing Display Search Login/Register
Bug Id ?
225
Reporter ?
jaredgeorge
MacGDBp / 1.4.1
Status ?
Unconfirmed
Severity ?
Major
Duplicate Of ?
- none -
Fixed in Revision ?
Mstone ?
Summary ?
Variable Inspector Limited To 1024 Characters
Report Time ?
June 30, 2011 07:39 PM
Assignment ?
Resolution ?
Open
Priority ?
Normal
Dependencies ?
- none -
Mstone (old) ?


Attachments
phpinfo_xdebug.txt phpinfo for xdebug
Votes
For: 2 (100%)
Against: 0 (0%)
Total: 2

June 30, 2011 07:39 PM jaredgeorge
It looks like the variable inspector will only display a maximum of 1024 characters. Are you able to replicate that? If so, any way to increase that? I often inspect very large strings (like SQL statements or dynamic HTML content). I also noticed that large arrays have a limit to the number of indices I can inspect (looks like you already know about the array issue in bug #212).

I tried to increase xdebug.var_display_max_data, *_depth, *_children, etc. but it doesn't seem to help. Thanks!

June 30, 2011 07:44 PM jaredgeorge
Attached is my phpinfo for the xdebug binary that I'm loading in MAMP.

December 14, 2012 12:37 AM Drew J. Sonne
I'm also getting exactly a max of 1024 characters. I've also tried the configuration options here here, and have found no change.

January 29, 2019 09:29 AM outis
This is most likely due to XDebug's `max_data` feature (https://xdebug.org/docs-dbgp.php#feature-names). It can be changed via the `feature_set` DBGP command; as far as I'm aware, that's the only way.