|
| Re: xdebug NegativeArraySizeException [message #613808 is a reply to message #609254] |
Tue, 21 September 2010 21:41   |
Eclipse User |
|
|
|
Originally posted by: dkel50.hotremovemail.com
Initial thought is that there is some problem at the server end. It
looks like something is sent to PDT as a socket has been established but
whatever gets sent to PDT is certainly not expected. If xdebug is not
creating a log then xdebug is not able to communicate with PDT.
If xdebug did establish a socket with PDT then it should send the init
string and that would at least be in the log.
You could try changing the ports that xdebug and PDT will communicate on.
Dave Kelsey
On 21/09/2010 21:45, Hugh Messenger wrote:
> Running Eclipse 3.6.0 with PDT 2.2.0 on Windows 7, everything up to date.
>
> Woke up this morning, started an xdebug session ... and it hangs at 24%,
> "Waiting for XDebug session". Tried restarting Eclipse. Tried restarting
> httpd on the (remote) server. Tried rebooting my machine and the server.
> Nada.
>
> I can see the session attempting to open from the server end, but it
> sticks at "SYN_SENT". I can see a listener open on the Eclipse machine.
>
> Tried getting an xdebug log, but for some reason the xdebug.remote_log
> INI directive isn't opening a log.
>
> Only clue is in the Eclipse log:
>
> !ENTRY org.eclipse.php.debug.core 4 4 2010-09-21 15:21:48.632
> !MESSAGE class
> org.eclipse.php.internal.debug.core.xdebug.communication.XDe
> bugCommunicationDaemon : Unexpected Exception: Listener thread still
> listening
> java.lang.NegativeArraySizeException
> at org.eclipse.php.internal.debug.core.xdebug.dbgp.session.DBGp
> Session.readResponse(DBGpSession.java:537)
> at org.eclipse.php.internal.debug.core.xdebug.dbgp.session.DBGp Session.
> <init>(DBGpSession.java:87)
> at org.eclipse.php.internal.debug.core.xdebug.communication.XDe
> bugCommunicationDaemon.startConnectionThread(XDebugCommunica
> tionDaemon.java:136)
> at org.eclipse.php.internal.debug.core.daemon.AbstractDebuggerC
> ommunicationDaemon$ReceiverThread.run(AbstractDebuggerCommun
> icationDaemon.java:206)
> at java.lang.Thread.run(Thread.java:619)
>
>
> I haven't changed anything .... everything was working when I hit the
> sack at 3am this morning ... was broken when I surfaced at noon ...
>
> Any suggestions VERY gratefully accepted. I'm dead in the water ... :(
>
> -- hugh
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.04013 seconds
] 
Search
Help
Register
Login
Home
