| Summary: | Crash in background parser on KDevelop shutdown | ||
|---|---|---|---|
| Product: | [Developer tools] kdevplatform | Reporter: | Niko Sams <niko.sams> |
| Component: | language | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | david.nolden.kde, tobias.hochguertel |
| Priority: | NOR | Keywords: | investigated, triaged |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
KDEV_SESSION={7f04ae30-167d-463a-9d90-ebab5fcc932c} valgrind ~tobi/Projekte/compiled/kde4/bin/kdevelop.bin |
||
|
Description
Niko Sams
2010-02-14 19:37:56 UTC
This probably needs a valgrind run. I can't see how the ksharedptr desctructor can crash right now. Created attachment 40975 [details]
New crash information added by DrKonqi
Same Issue here, but additional I cannot see the opened files in the editor, only the document tab shows me a list of opend files, but I cannot see the file contents.
Really we need a valgrind run for this, so anybody who can reproduce this, please run KDEV_SESSION={.....} valgrind kdevelop.bin (where {...} is the uuid from your session visible in kdevelop --sessions) and provide the output here.
Created attachment 40977 [details]
KDEV_SESSION={7f04ae30-167d-463a-9d90-ebab5fcc932c} valgrind ~tobi/Projekte/compiled/kde4/bin/kdevelop.bin
tobi@tobias-ws:~$ kdevelop --sessions
Available sessions (use '-s HASH' or '-s NAME' to open a specific one):
Hash Name: Opened Projects
{7f04ae30-167d-463a-9d90-ebab5fcc932c} hedge [running]
WARNING: deleting stale lockfile /home/tobi/.kde/share/apps/kdevelop/sessions//{bda40a79-bf37-4550-a115-261dea66cdf3}/lock
{bda40a79-bf37-4550-a115-261dea66cdf3} hedge
The KDEV_SESSION={7f04ae30-167d-463a-9d90-ebab5fcc932c} valgrind ~tobi/Projekte/compiled/kde4/bin/kdevelop.bin Command Output is in the Attachment..
Did kdevelop really crash with this valgrind log? It doesn't seem to include any trace of the crash. (the conditional jump depends on uninitialized value errors are afaik false positives) The only thing I can see is an X11 error when data is retrieved from the clipboard, but this is something you'd need to take to Qt/Nokia or x.org. oh sorry ;) my Fail. I'm new :) I haven't crashed the application again with the valgrind command, I will later try it to crash it with valgrid running, I think at the evening I have some time. ~ 20:00 I don't see any KSharedPtr within ParseJob at all, so this crash is strange. 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! 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! |