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 126383

Summary: Redundant debugger warning
Product: php Reporter: Mikhail Matveev <mikhailmatveev>
Component: DebuggerAssignee: rmatous <rmatous>
Status: VERIFIED FIXED    
Severity: blocker    
Priority: P3    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:
Bug Depends on:    
Bug Blocks: 123477    

Description Mikhail Matveev 2008-01-31 12:53:55 UTC
1. Create new PHP file.
2. Run debugger.
3. Click Finish debugger session button.
Result: after some time, a warning "No connection from remote debugger" appears. It's wrong: debugger session is
finished correctly, and there is no need for this warning.
Comment 1 Petr Pisl 2008-06-19 13:42:44 UTC
I think this is already fix, but to be sure reassigning to Radek, who is no responsible for the debugger.
Comment 2 rmatous 2008-06-23 16:54:03 UTC
Really, Fixed
Comment 3 Mikhail Matveev 2008-06-30 15:45:33 UTC
Still exists in M1. Now warning is: "There is no connection from xdebug detected within 19 seconds. The reasons could
be..." and so on
Comment 4 rmatous 2008-06-30 16:20:45 UTC
Debugger waits for connection with the engine as soon as the debugging session was started. If connection is established
the state is somehow signalized in progress bar (at least the text is changed). After that, you can use debugger (like
step in/out/over and so on). If you now stop the session you should see no warning. If you stop the session before
connection is established (maybe because xdebug no installed or not properly configured) then you should see warning.
Simply the warning says what has happened: "There is no connection from xdebug detected within 19 seconds ... Is it
wrong or is the text wrong or doesn't behave for you as I described? Explain and reopen, comment if you still believe
this issue deserves to be reopened.

Comment 5 Mikhail Matveev 2008-09-08 16:17:05 UTC
I agree that debugger warning is correct.