From kdevelop-bugs Thu Apr 26 08:33:19 2012 From: jay Date: Thu, 26 Apr 2012 08:33:19 +0000 To: kdevelop-bugs Subject: [Bug 298840] New: kdev-xdebug : recieves only 'stopping' not 'stopped' state Message-Id: X-MARC-Message: https://marc.info/?l=kdevelop-bugs&m=133542940716447 https://bugs.kde.org/show_bug.cgi?id=298840 Bug ID: 298840 Severity: minor Version: git master Priority: NOR Assignee: kdevelop-bugs@kdevelop.org Summary: kdev-xdebug : recieves only 'stopping' not 'stopped' state Classification: Unclassified OS: Linux Reporter: jay@jay.cz Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kdevelop These are the last lines from xdebug remote.log -> Log closed at 2012-04-26 08:06:38 (tested xdebug versions 2.0.1, 2.1, git) I don't know the history, but now xdebug does not send 'Stopped' state, as kdev-xdebug plugin expects. In the diff bellow I changed Stopping method to Stopped, and it works for me. Reproducible: Always Steps to Reproduce: 1. start debugging on a simple file, without breakpoints. Actual Results: Even after the script comes to its end, kdevelop and browser still treat it like running (browser is stil loading the page, even it already has the content) When I 'hover' mouse over some variable, kdev-xdebug tryes to retrieve that value from xdebug, and than it gets the report that the script already finished. Expected Results: After the end of script, browser should stop loading, and variables panel in kdevelop should clean up. Modification of kdev-xdebug, which solves it for me: diff --git a/connection.cpp b/connection.cpp index a5f2d38..c8a6338 100644 --- a/connection.cpp +++ b/connection.cpp @@ -149,7 +149,7 @@ void Connection::processResponse(const QDomDocument &xml) if (status == "running") { setState(DebugSession::ActiveState); } else if (status == "stopping") { - setState(DebugSession::StoppingState); + setState(DebugSession::StoppedState); } else if (status == "stopped") { setState(DebugSession::StoppedState); } else if (status == "break") { -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ KDevelop-bugs mailing list KDevelop-bugs@kdevelop.org https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs