| Summary: | KDevelop random crash | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | rgoomes <ricardo.jpg> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | jr |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
rgoomes
2018-11-20 15:47:13 UTC
@Riddell: KDevelop on Neon is still using LLVM 5.0? Could you try to upgrade this to the latest available LLVM version? @Reporter: Which project was loaded? Can you disclose the source code? Can you nail down which file KDevelop was parsing last (please check the debug output on the terminal for this)? (In reply to Kevin Funk from comment #1) > @Riddell: KDevelop on Neon is still using LLVM 5.0? > > Could you try to upgrade this to the latest available LLVM version? I have both LLVM 5.0 and 6.0 versions installed and the default is the LLVM 6.0. I need LLVM 5.0 because some package depends on it and so I can't uninstall it. I think it should be up to KDevelop to choose the newest LLVM Our KDevelop builds against llvm-5.0-dev. I can switch that to llvm 6 if that helps which is the default in Ubuntu 18.04 The later the better usually. Thanks for taking care of it! (In reply to Kevin Funk from comment #2) > @Reporter: Which project was loaded? Can you disclose the source code? > > Can you nail down which file KDevelop was parsing last (please check the > debug output on the terminal for this)? Unfortunately, this is a closed source project. I can't provide this info. New build of kdevelop 4:5.3.0-0xneon+18.04+bionic+build7 uses llvm and clang 6 in line with mesa and other parts of Ubuntu 18.04. This may stop symbols clashes. (In reply to Jonathan Riddell from comment #7) > New build of kdevelop 4:5.3.0-0xneon+18.04+bionic+build7 uses llvm and clang > 6 in line with mesa and other parts of Ubuntu 18.04. This may stop symbols > clashes. Thanks, testing right know the new build. > This may stop symbols clashes
Should not have been a problem in this case. This rather seems like a crash in libclang while parsing code.
(In reply to Kevin Funk from comment #9) > > This may stop symbols clashes > > Should not have been a problem in this case. This rather seems like a crash > in libclang while parsing code. I'm not able to reproduce the crash anymore. I think you can mark this as RESOLVED / FIXED. Thanks for feedback. I presume the LLVM/Clang upgrade did the trick. |