This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 188081 - Socket Exception when xdebugging test files
Summary: Socket Exception when xdebugging test files
Status: RESOLVED INCOMPLETE
Alias: None
Product: php
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Ondrej Brejla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-25 03:35 UTC by jontyc
Modified: 2011-09-26 13:04 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE Log file (30.22 KB, text/plain)
2010-06-25 03:35 UTC, jontyc 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jontyc 2010-06-25 03:35:58 UTC 
Created attachment 100413 [details]
IDE Log file

I've read previous bug reports of socket exceptions occurring a few months ago when variables are hovered over, but this is different. My xdebug works perfectly on Source Files.

I go to debug a unit test file in the PHPUnit Test Files directory, again the debugger works fine, until I stop the debugger. Then I get a socket exception.

I can then no longer debug (xdebug won't connect again) until I exit netbeans and restart netbeans.

Xdebug 2.1.0rc1
PHPUnit 3.4 (pretty sure, how can I verify this?)
Comment 1 jontyc 2010-06-25 03:39:08 UTC 
To reproduce, all I need to do is right-click a test file, debug, (debugger set to stop on first which it does), then Finish Debugger Session.

Socket Exception message - the one telling you to make sure there are no watches (which there aren't).

I have tried both wiping out the userdir and recreating my project from scratch after deleting nbproject directory.

Problem still exists.
Comment 2 jontyc 2010-06-25 06:01:15 UTC 
Another observation: 

If the debugger is not manually stopped and the test runs to completion (or to error), no socket exception will occur and the debugger can be run again without issue.
Comment 3 Filip Zamboj 2010-09-15 12:32:08 UTC 
batch reassigning
Comment 4 OndrejBrejla 2011-03-29 12:58:48 UTC 
I'm not able to reproduce it. Can you check if the bug still appears in NB 7.0RC1? If it appears, can you attach the simplest test file, which causes that exception? Thanks.
Comment 5 Tomas Mysik 2011-06-03 10:19:03 UTC 
Batch reassigning.
Comment 6 Tomas Mysik 2011-06-09 13:20:45 UTC 
Reassigning to the module owner.
Comment 7 Ondrej Brejla 2011-09-26 13:04:20 UTC 
No response from reporters and I'm not able to reproduce it.