https://bugs.kde.org/show_bug.cgi?id=397822
Bug ID: 397822
Summary: kdevelop ASSERT: "d->m_process->state() ==
QProcess::NotRunning || !killSuccessful" when trying
to kill crashing test
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: fa...@kde.org
Target Milestone: ---
Run a unittest with Ctrl+R, which runs into a crash like using deleted memory,
which ends up in glibc calling gdb internally to give a stacktrace.
While that's happening (it can take quite a while), click "Stop All" in the
toolbar.
kdevplatform.outputview:
KDevelop::OutputExecuteJob::doKill|KJob::kill|KDevelop::ExecuteCompositeJob::doKill
Could not kill the running process: QProcess::ProcessError(Timedout)
?libKDevPlatformOutputView.so.52?|?kdevexecute.so? ASSERT:
"d->m_process->state() == QProcess::NotRunning || !killSuccessful" in file
/d/kde/src/5/extragear/kdevelop/kdevelop/kdevplatform/outputview/outputexecutejob.cpp,
line 109
Great, now I have two crashes instead of one :-)
--
You are receiving this mail because:
You are watching all bug changes.
