I was trying to debug a rather large object today (a Propel ORM object) and noticed that the instance var I was trying to debug was not displayed when I "opened" the $this variable.

The variable is named "aPhotographer" and is a protected instance var. In fact, a large number of variables are missing. Only 32 are shown. No others.

It seems that it might be related to the order in which the variables are defined in the class... because I don't see any variables that appear lower in the file than a particular variable.

Hope that helps.

I just confirmed the limitation by re-arranging the order of variable definitions and they appear as expected, and other ones disappear.

Hopefully this will allow you to fix the bug!

I really love MacGDBp. BTW the 1.4 beta works over a remote connection *MUCH* faster, thanks!

What version of Xdebug are you using? I think this may be an issue with the extension, unfortunately.

php5-xdebug @2.1.0_0 via macports

This is not a limitation of the debug protocol. What's happening is the following:

The code is only getting properties like this:

property_get -d %d -n %@

Which, for a large variable, will return with XML something like this:

<property name="$node" fullname="$node" address="4334972112" type="object" classname="stdClass" children="1" numchildren="62" page="0" pagesize="32">

So because pagesize is less than numchildren, we're only getting the first 32 of (in this case) 62 properties.

What should be happening is you should requesting

property_get -d %d -n %@ -p {page number}

when the callback is executed for the additional pages.

Another option would be to do a set the feature for max_children to be something arbitrarily large.

Jon, do you think something similar could be happening with very long string variables? I submitted ticket 225 (http://www.bluestatic.org/bugs/showreport.php?bugid=225) where string values are limited to 1024 characters in the inspector. Just hoping the next revision might resolve that so I can get rid of NetBeans once and for all! =)