| Summary: | Crash, after close KDevelop (using NXClient) | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Phantom <rmilki> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | aleixpol, sergeikrivonos |
| Priority: | NOR | Keywords: | triaged |
| Version First Reported In: | 4.2.3 | ||
| Target Milestone: | 4.2.3 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Phantom
2011-10-05 23:55:42 UTC
It would be interesting if you could provide a backtrace with debug information. There's not much we can do with this backtrace. Created attachment 70785 [details]
New crash information added by DrKonqi
kdevelop (4.2.3) on KDE Platform 4.8.1 (4.8.1) using Qt 4.7.4
Used it for a while. Edited cmake project. Several application debugging sessions. Crashed on close.
-- Backtrace (Reduced):
#14 0x00000000004053c9 in _start ()
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 set the bug status 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! (In reply to Aleix Pol from comment #1) > It would be interesting if you could provide a backtrace with debug > information. There's not much we can do with this backtrace. Hi Alex, see all threads are waiting except thread 9. Please, take a look if QEventDispatcherGlib::~QEventDispatcherGlib could cause the abort. It may be fixed long time ago this. 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. |