Summary: | Kdevelop crashes during parsing | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | claas.koehler |
Component: | Build tools: CMake | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | crash | CC: | aleixpol |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | 4.2.3 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Valgrind log |
Description
claas.koehler
2012-01-14 16:24:17 UTC
Created attachment 67827 [details]
Valgrind log
Can you provide an example of the code that triggers this crash? (In reply to comment #2) > Can you provide an example of the code that triggers this crash? Unfortunately the project causing the problem is proprietary. Sorry. Claas Well, it's possible that's already solved, or not. If you can make another script to reproduce the problem, that would be helpful. Until then, I'm closing as invalid. I just pulled the latest trunk, and the problem still persists. I could not manage to create a simple test case, which shows similar behaviour. Thus the problem is definitely not fixed and I suggest changing the status back to unconfirmed. If I can assist you in debugging by providing more output or if you could point me in a direction, I could attempt to do further debugging myself, although I have to admit that I am not familiar with the kdevelop sources. Regards Claas As I said, please provide a problematic example that I can reproduce. With closed project, people usually provide the cmake sources without the C++, but of course the smaller it is, the better. aleix, it's pretty easy to see that this might be an issue though just by looking at the sources: you do: list->elements().first(). What if elements() is empty? It asserts! I think from that you should be able to construct a ListAst::Find unit test with empty elements, no? bye |