| Summary: | kdevplatform: TypeRegister crash in ObjC++ | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | RJVB <rjvbertin> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version: | 5.1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=379669 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
RJVB
2017-07-07 13:56:06 UTC
FWIW, I this was printed on the terminal: kdevplatform.language: Factory for this type not loaded: 51 KCrash: Application 'kdevelop' crashing... KCrash: Attempting to start /opt/local/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/505/kdeinit5__0 QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 25 and type 'Read', disabling... QSocketNotifier: Invalid socket 34 and type 'Exception', disabling... QSocketNotifier: Invalid socket 157 and type 'Read', disabling... QSocketNotifier: Invalid socket 173 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 29 and type 'Read', disabling... QSocketNotifier: Invalid socket 174 and type 'Read', disabling... QSocketNotifier: Invalid socket 32 and type 'Read', disabling... QSocketNotifier: Invalid socket 167 and type 'Read', disabling... QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 30 and type 'Read', disabling... The X11 connection broke (error 1). Did the X11 server die? FunctionDeclarationData::m_defaultParameters There were items left on destruction: 1484 ClassFunctionDeclarationData::m_defaultParameters There were items left on destruction: 57 ClassDeclarationData::baseClasses There were items left on destruction: 250 DUContextData::m_uses There were items left on destruction: 4516 MacroDefinitionData::parameters There were items left on destruction: 2282 TopDUContextData::m_problems There were items left on destruction: 201 ProblemData::diagnostics There were items left on destruction: 4717 TopDUContextData::m_usedDeclarationIds There were items left on destruction: 201 DUContextData::m_localDeclarations There were items left on destruction: 1985 DUContextData::m_importers There were items left on destruction: 210 DUContextData::m_childContexts There were items left on destruction: 378 DUContextData::m_importedContexts There were items left on destruction: 175 Unable to start Dr. Konqi (The last bit was clearly false alarm and I have no idea if the X11 error indeed came from KDevelop) I haven't yet been able to reproduce the crash, maybe it was a freak even related to outdated/incompatible duchain cache data, so simply due to parsing a Cocoa ObjC++ file on Linux (I do have the SDK headers installed and added to the compiler search path btw). Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |