Bugzilla – Full Text Bug Listing
| Summary: | Irregular state control | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Toshihiro Izumi <euthanasia_waltz> |
| Component: | PDT | Assignee: | Shalom Gibly <shalom> |
| Status: | CLOSED FIXED | QA Contact: | Yossi Luson <yossi.l> |
| Severity: | minor | ||
| Priority: | P2 | CC: | gadi, spektom |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Modified the code according to your suggestion. Since this situation occurs sometimes, testing it will take some more time before we can say this problem is behind us. Thank you Toshihiro!!! Appreciate your help! *** Bug 169004 has been marked as a duplicate of this bug. *** Yosi: couldn't recreate this bug I've re-created this bug on Fedora virtual box machine. More fixes where needed in PHPDebugTarget :) |
*Sometimes* PHPIDE does not respond when I carried out StepInto. PHPIDE shows 'running' state so I have to select process|thread and click 'Suspend' button. org.eclipse.php.debug.core.model.PHPDebugTarget#stepInto() >protected void stepInto() throws DebugException { > Logger.debugMSG("[" + this + "] PHPDebugTarget: stepInto "); > fLastcmd = "stepInto"; > fStatus = debugger.stepInto(fStepIntoResponseHandler); > if (!fStatus) { > Logger.log(Logger.ERROR_DEBUG, "PHPDebugTarget: debugger.stepInto return false"); > } > int detail = DebugEvent.STEP_INTO; > resumed(detail); >} IMO, 'resumed(detail)' should be carried out before invoking 'debugger.stepInto()'. Usually the state of the IDE flows suspended -> running(resumed) -> suspended. If response of debugger is too quick, the state of the IDE flows suspended -> suspended -> running(resumed). PHPDebugTarget#stepOver() is same. (or worse) Don't omit firing event.