| Summary: | Kdevelop crashes when clicking "Stop All" | ||
|---|---|---|---|
| Product: | [Developer tools] kdevplatform | Reporter: | Gerard <thatnewyorker> |
| Component: | shell | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version First Reported In: | 5.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| URL: | https://phabricator.kde.org/R32:71f7bed96dd0954635c2793c681ba8a5da9ba318 | ||
| Latest Commit: | https://phabricator.kde.org/R32:71f7bed96dd0954635c2793c681ba8a5da9ba318 | Version Fixed/Implemented In: | 5.2.2 |
| Sentry Crash Report: | |||
|
Description
Gerard
2018-03-31 14:28:45 UTC
Hm, I don't see anything wrong in the code in kdevplatform here.
The location where the crash is happening is likely:
```
#if QT_VERSION < 0x050600
connect(process, static_cast<void(QProcess::*)(QProcess::ProcessError)>(&QProcess::error),
#else
connect(process, &QProcess::errorOccurred,
#endif
this, [](QProcess::ProcessError error) {
qCWarning(SHELL) << "process finished with error:" << error;
});
```
Specifically, this line seems to cause a crash:
> qCWarning(SHELL) << "process finished with error:" << error;
But: I don't see how `error` can be corrupted, also given that the QProcess instance is still fully intact at that time...
Ah, that code changed recently. Issue fixed by: https://phabricator.kde.org/R32:71f7bed96dd0954635c2793c681ba8a5da9ba318 Thus fixed in 5.2.2 (to be released). Well that's good to know. |