[521] Frequent XDebug disconnects

I'm not even sure how to go about debugging this...

XDebug is disconnecting in the middle of virtually every debug session that takes more than a few seconds to run.  It happens almost every time I try to get mouseover context for a variable, add a watch, etc. but it also just happens without warning just when stepping through code.  Is there any known issue that would be causing this?


PHP 5.3.2-1ubuntu4.5 with Suhosin-Patch (cli) (built: Sep 17 2010 13:49:46)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies
    with XCache v1.3.0, Copyright (c) 2005-2009, by mOo
    with Xdebug v2.0.5, Copyright (c) 2002-2008, by Derick Rethans
    with Suhosin v0.9.29, Copyright (c) 2007, by SektionEins GmbH

10 comments
Comment actions Permalink

Timeout. You have to set three variables.

In your php.ini, set your

max_execution_time = <something long, I use 700 seconds>

The other two depend on Apache or IIS.

Here are mine for IIS 7.

timeout1.JPG

0
Comment actions Permalink

No, it's definitely not execution-time related.  It can happen in the first second of execution.  (And debugging is supposed to disable execution time limits, anyway - it has with every IDE I've ever used.)

It typically happens when the IDE is doing 'communication' with the debug server.  As I said - it is almost always reproducable simply by mousing over a variable to get context.

0
Comment actions Permalink

signe wrote:

No, it's definitely not execution-time related.  It can happen in the first second of execution.  (And debugging is supposed to disable execution time limits, anyway - it has with every IDE I've ever used.)

It typically happens when the IDE is doing 'communication' with the debug server.  As I said - it is almost always reproducable simply by mousing over a variable to get context.


Oh, that might not be your issue, but with PHP, that is not the case. Timeouts have to be changed (default is like 30 seconds) or it will disconnect.

0
Comment actions Permalink

Hello signe,

There are a lot issues about evaluation in XDebug.

   with Xdebug v2.0.5, Copyright (c) 2002-2008, by Derick Rethans


I recomend you to use the latest stable XDebug version(2.1.0) - http://xdebug.org/download.php.

Also please provide me PhpStorm debugging log(http://devnet.jetbrains.net/docs/DOC-1202) and xdebug native log(xdebug.remote_log - http://xdebug.org/docs/remote).

Thank you for your feedback!

0
Comment actions Permalink

Ok - I think I figured out what was causing the disconnects (another client was auto-refreshing the page and restarting the debug session [maybe?]),  but there are definitely still some issues with variables.  Using the Variables panel won't expand beyond the first child.

i.e.
it will turn $this into $this->children
but it won't expand $this->children into $this->children->subchildren

Unfortunately, our servers are running Ubuntu 10.4 (LTS), so upgrading xdebug isn't quite as simple as it sounds.  This version of xdebug is going to be around for quite a while due to its inclusion in Ubuntu (3 years of support beginning April 2010), so it would be better if you guys can try and figure out what interop issues exist with it.

I can provide logs, but I'm a little security-wary.  Is there a private place to do so?

0
Comment actions Permalink

Sorry, but that's not true.  Debugging keeps the process alive and prevents any timeouts, otherwise debugging would be virtually impossible to complete.  I've been coding PHP for 12 years, and using line-debugging IDEs for at least the last 8.  I have, and do, leave debugging processes open for hours while I'm working without any additional timeouts required.

0
Comment actions Permalink

It is simply not the case on Windows with IIS and FastCGI. The FastCGI module will simply terminate PHP instance if it is running longer than specified amount of seconds or/and if it will not receive any output from it during another specified time interval (those settings were presented on a screenshot). And any PHP debugger (Xdebugger, ZendDebugger etc) will not help here.

You are on Linux (which most likely means Apache) -- you have different rules.

0
Comment actions Permalink

If you do not want to upgrade xdebug on server itself, you can always replicate it on virtual machine (clone real system somehow or make fresh intall on VM) -- there you can safely install latest stable xdebug build and test debugging process.

it won't expand $this->children into $this->children->subchildren

Here is the ticket that matches your description: http://youtrack.jetbrains.net/issue/WI-4312?projectKey=WI

I can provide logs, but I'm a little security-wary.  Is there a private place to do so?

Wait for new build and try it -- the above issue is marked as fixed. If it still will not work for you -- you can submit new ticket on issue tracker where you can limit access to attachments where only JB staff can see and access them.

0
Comment actions Permalink

Hello signe,

98.521 EAP brought several regressions related to XDebug. Most critical issues were fixed in our latest EAP - 100.36.

but there are definitely still some issues with variables.  Using the Variables panel won't expand beyond the first child.

WI-4312 -  fixed in EAP 100.36.

I can provide logs, but I'm a little security-wary.  Is there a private place to do so?


Please create a bug request in our bugtracker http://youtrack.jetbrains.net/issues/WI and attach your log there with visitibility restriction to 'idea-developers' group.(Look at attached pictures)

Thank you for your feedback!



Attachment(s):
attach_step2.png
attach_step1.png
0
Comment actions Permalink

Hello signe,

Do you still have this issue?

0

Please sign in to leave a comment.