| Summary: | KDevelop crashed a view seconds after the sourcecode of my project occurs [Php::ExpressionEvaluationResult::setDeclarations] | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Tom <tom> |
| Component: | Language Support: PHP | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.0.2 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Tom
2016-11-24 22:53:56 UTC
The crash happens inside our PHP language support plugin. Is the project you're working on open-source? Can you share the source code so we can try to reproduce the problem? If not, could you install debug symbols so the backtrace contains more info (line numbers, stack values, etc.)? Dear Kevin, the Project is only a Set of PHP-Scripts. Nothing tricky in there (except the smart code :) ) After i commit the Bug-Report, i restart KDevelop and it crashed again. I attempted to open KMail and it dosn´t start too. So i figured out, that Akonadi is not running well. I repaired Akonadi (rm -rf ~/.local/share/akondai) and KMail starts well. After a while i tryed to start KDevelop and it start´s without an issue. Can it be, that akonadi has a influence to/after the start of KDevelop ? kr Tom PS: it´s happend after a system-upgrade from FC24 to FC25 No, KDevelop has nothing to do with Akonadi. Can you share your source code? Zip & upload somewhere where we can download it? Dear Kevin, Thank you for your support and fast response. Could you explain what is important on the Sourcecode of my project (that i can´t share)? If you asked me about the XML-Files for Syntax highlighting, i see a little context to the crash. But the source that would be displayed has -which- connection to a crash ? Never mind. I worked with KDevelop in the last hours without an issue and i think a "onetime crash" would be acceptable :) If the crash happens again similar in kind, i will reopen this BUG-Report. kr Tom KDevelop has a parser + static analyzer for source code, the crash happens there. That information is also used for highlighting. What triggers the crash is often or at least sometimes a specific piece of code which leads to the analyzer taking a crashy codepath. This kind of bug is only reproducible if we have the code triggering it. Anyways, if it doesn't happen every time, then that's not the case here. |