| Summary: | settings->configure Kdevelop->source formatter crashes | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | bruno chareyre <bruno.chareyre> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | Keywords: | investigated, triaged |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | 4.1.0 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
valgrind output
another valgrind output |
||
|
Description
bruno chareyre
2010-11-03 17:57:37 UTC
if this is reproducible in KDevelop 4.1, please run kdevelop through valgrind and show us the log it creates: valgrind --track-origins=yes --num-callers=25 kdevelop this works fine for me btw. > this works fine for me btw.
>
It used to work for me too.
Valgrind report is attached.
I see I have KDevelop 4.0 from lucid, not 4.1. Created attachment 53104 [details]
valgrind output
In kdev 4.0 the valgrind call is different:
kdevelop --sessions # find your {...} session hash
KDEV_SESSION={...your-hash...} valgrind --track-origins=yes --num-callers=25 kdevelop.bin
Created attachment 53254 [details]
another valgrind output
I'm sending the log with the new command, but not sure you'll find what you need in there. Kdevelop hangs before I can do anything (I waited 15min, then got a "not responding" message), so I could not reproduce the original bug itself, sorry. I'm sending this report in case there is already a trace of the problem at startup, by any chance...
no, nothing related shown in there. and you should think about installing more debug symbols / compiling from sources, so we get exact line numbers and such - would be very helpful. I add no much time to investigate more. I deleted all ~.kde/kdev* files and now the problem seems to be solved. I will not be able to reproduce it, sorry. 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! |