Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DebuggerStatus: Only ten visible elements in Perl hash or list that is greater #183

Closed
crayday opened this issue Sep 25, 2014 · 4 comments · May be fixed by #248
Closed

DebuggerStatus: Only ten visible elements in Perl hash or list that is greater #183

crayday opened this issue Sep 25, 2014 · 4 comments · May be fixed by #248
Labels
on hold

Comments

@crayday
Copy link

crayday commented Sep 25, 2014

Thank you very much for such a nice experience with Vim and Perl!

However I've encountered some problems. When I'm expanding hash or list in DebuggerStatus window, I can see only ten elements, even if there're more. It look's like this:

 ⬦ $AdditionalData = (array)
 ▾ $ArtProp = (hash [53])
   ⬦ $ArtProp->{adult} = (scalar [2]) `12`
   ⬦ $ArtProp->{adult_annotation} = (scalar [1]) `0`
   ⬦ $ArtProp->{adult_cover} = (scalar [1]) `0`
   ⬦ $ArtProp->{allow_drm} = (scalar [1]) `0`
   ⬦ $ArtProp->{allow_online_reading} = (scalar [1]) `0`
   ⬦ $ArtProp->{art_age} = (scalar [8]) `180.6633`
   ⬦ $ArtProp->{'author-name'} = (scalar [17]) `Макс Фрай`
   ⬦ $ArtProp->{'author-name-dateln'} = (scalar [19]) `Максу Фраю`
   ⬦ $ArtProp->{'author-name-predl'} = (scalar [19]) `Максе Фрае`
   ⬦ $ArtProp->{'author-name-rodit'} = (scalar [19]) `Макса Фрая`
 ⬦ $ID = (scalar [7]) `6689025`

In this example hash consists of 53 elements but I can view only 10 of them.

I don't know, maybe this is not a problem with Vdebug. Can you please give any advice on solving this problem or confirm it as a bug?

Sorry for my russian-english.
@exussum12
Copy link

I have the same issue, I usually do :VdebugEval and use a function to write the output to a file then read the file

Its not great i know but it does work

@joonty
Copy link
Collaborator

joonty commented Sep 26, 2014

Hi, thanks for the feedback!

I'll be honest, I never use Perl. The fact that you use it regularly and
find that it more or less works is great. I know that the debugging engine
is a bit flakey, so some of it may be down to limitations there. But I'll
dust off my Perl binary and give it a try as soon as I can.

Sorry about the wait!

Thanks
On 26 Sep 2014 17:39, "Scott Dutton" [email protected] wrote:

I have the same issue, I usually do :VdebugEval and use a function to
write the output to a file then read the file

Its not great i know but it does work

—
Reply to this email directly or view it on GitHub
#183 (comment).

@exussum12
Copy link

Happens for me in PHP also, using php 5.3. Not tested on a more recent PHP. It shows the first x (x doesnt seem fixed, so it may be a xdebug limitation ?)

@joonty
Copy link
Collaborator

joonty commented Aug 18, 2015

This is ridiculously late, but you can use xdebug.var_display_max_children to change the number of array children returned by Xdebug. But it should default to 128, so I don't know why it's being random @exussum12. Try setting that var explicitly, and seeing whether that makes any difference.

@joonty joonty added the on hold label Aug 18, 2015
@niloct niloct mentioned this issue Jun 20, 2016
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
on hold
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Interface addons niloct/vdebug
4 participants
@BlackIkeEagle @joonty @exussum12 @crayday