Summary: | CRASH in moment of inserting row into editor | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Piotr Mierzwinski <piotr.mierzwinski> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | piotr.mierzwinski |
Priority: | NOR | ||
Version: | 4.7.0 | ||
Target Milestone: | --- | ||
Platform: | Mageia RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | full gdb log from running |
Description
Piotr Mierzwinski
2015-01-22 17:41:33 UTC
Created attachment 90586 [details]
full gdb log from running
Can you please check if that is reproducible? If yes, please add this information to the reported this bug is a duplicate of. *** This bug has been marked as a duplicate of bug 334487 *** I'm able to reproduce it. I did the same what I've described above and crash didn't happen. In last message should start with "I'm not able....", of course. Today the same crash happened me today. I did a bit similar actions what before. Maybe will be helpful. There were: 1. I've implemented one method in declaration file (h) 2. I've moved it to definition file (cpp) using "Move to code" option (Alt+Ctrl+S) 3. I've switched (F12) to definition file 4. I was trying put new line inside new method definition Unfortunately these steps can't always lead to crash. It happens sometime. I can provide backtrace from crash, but it's much similar to aforementioned and alternatively full log from gdb from which KDevelop was launched. Continue to my previous post. Unfortunately I've got the same crash as before. Passed half an hour. It's a bit annoying and for me KDevelop 4.7.0 seems to be not stable :(. I meet a crash couple times a day (at least yesterday and today). It's sad. Fortunately recovery function is irreplaceable in such situation. Seems to be very robust. I'm happy, having it in KDevelop. Back to problem. What I did this time? Below please find the steps: 1. I've started KDevelop again (using gdb). 2. All modified (not saved) 3 files have been recovered so I've saved them. 3. From one of the class where I used function* mentioned in previous message I've invoked option "Find Uses" being over calling of function. 4. Using "Code browser" view, I've jumped (clicking on url) to the first using of function (it was present in the same class like mentioned in point 3) 5. In function (where I jumped) I've removed local declarations of two members used in invoking of function and removed two arguments from invoking of function 6. KDevelop crashed *to be detailed it was overloading function, where in original were 3 arguments and in new one only one argument. After restart of KDevelop (using gdb as usual). I've repeated the same steps for all other invoking of function. KDevelop didn't crash, so this is not reproducible. I can provide backtrace from crash, but it's much similar to aforementioned and alternatively provide full log from gdb from which KDevelop was launched. And the same crash again. I will count it on 2015/01/23. :-/ As you can see it happens quite often (for me). Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xa34bfb40 (LWP 20905)] 0xb56eac66 in operator() (topData=0xa02f9f88, __closure=<synthetic pointer>) at /usr/src/debug/kdevplatform-1.7.0/language/duchain/topducontextdynamicdata.cpp:509 509 FOREACH_FUNCTION(const DUContext::Import& import, topData->m_importedContexts) I can provide backtrace from crash and full log from gdb from which KDevelop was launched. Here https://bugs.kde.org/show_bug.cgi?id=334487 you can find valgrind output for this bug. |