| Summary: | KDevelop is not able to recover from clang crashes | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Anton Kreuzkamp <akreuzkamp> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | The file to reproduce the clang and therefore the kdevelop-crash | ||
|
Description
Anton Kreuzkamp
2018-04-29 15:46:54 UTC
Created attachment 112306 [details]
The file to reproduce the clang and therefore the kdevelop-crash
It's already enough to open the file without a project.
Assuming the decision that libclang runs in-process, there is not really anything KDevelop can do about this ... the CrashRecovery stuff is from libclang itself. The reason for the crash needs to be fixed upstream. |