Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9225683
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T04:38:33+00:00 2026-06-18T04:38:33+00:00

I am using this vim plugin https://github.com/ludovicPelle/vim-xdebug with xdebug Xdebug and the vim plugin

  • 0

I am using this vim plugin https://github.com/ludovicPelle/vim-xdebug with xdebug

Xdebug and the vim plugin are working fine with regular scripts. I can step through and print out variables.

When I try to step through a basic unit test, it gets to the breakpoint fine and stops, and I can step through the code ok, but I can no longer view the contents of variables.

I am trying to get this to work with a very basic unit test

class testClass extends \PHPUnit_Framework_TestCase
{
  public function testSomething()
  { 
    $a = 5;
    $b = 6;
    $c = 7;
  } 
}

When I step to the end of the method and try to print out the contents of $a, I get the following error.

13 : send =====> property_get -i 13 -d 0 -n a
13 : recv <===== {{{   <?xml version="1.0" encoding="iso-8859-1"?>
<response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="property_get" transaction_id="13" status="break" reason="ok"><error code="300"><message><![CDATA[can not get property]]></message></error></response>
}}}
response status=break xmlns=urn:debugger_protocol_v1 xmlns:xdebug=http://xdebug.org/dbgp/xdebug reason=ok command=property_get transaction_id=13
error code=300 : Can not get property (when the requested property to get did not exist, this is NOT used for an existing but uninitialized property, which just gets the type "uninitialised" (See: PreferredTypeNames)).
    message
        can not get property

When I print out the whole context the 3 variables show up as follows

$command = 'context_get';
 a                    = /* uninitialized */'';
 b                    = /* uninitialized */'';
 c                    = /* uninitialized */'';

I know that phpunit does some interesting tricks when it runs the methods of a test class, so that might be why the debugger isn’t returning the variables in the method. Any suggestions would be greatly appreciated, thanks.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-18T04:38:35+00:00Added an answer on June 18, 2026 at 4:38 am

    The problem turned out to be the version of xdebug I was using, apparently this is a known issue in 2.0 which was fixed in 2.1 The virtual machine I am debugging on is ubuntu 10.04 LTS

    At the time that this version of Ubuntu was released xdebug 2.1 was still a release candidate. I compiled the most recent version of xdebug and I am able to view the variables within a method.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm using Vim with EasyMotion plugin. My current .vimrc is following: https://github.com/iAdramelk/.dotfiles/blob/master/vimrc I'd like
I found this plugin: http://vim.wikia.com/wiki/Find_files_in_subdirectories to be really useful to find a file(s) using
Using vim with the Rails plugin, can you create a migration file and then
I'm using Vim (7.2.445 on Debian Squeeze) with the vim-snipmate plugin (specially this fork
I came across this question: https://softwareengineering.stackexchange.com/questions/87077/how-can-a-code-editor-effectively-hint-at-code-nesting-level-without-using-inde and thought that Vim might be able to
I am using Taglist plugin in vim. In the taglist window i can see
I'm using this vim plugin for coffeescript and I want to keep all my
I am using DrawIt plugin in Vim 7 to draw some ASCII diagrams. This
I'm using vim with the vim-golang plugin. This plugin comes with a function called
This popped-up while writing a script for vim. Using the well-documented ':normal' command: :normal

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.