Summary: | Kdevelop crashes when executing the tool Configure in Custom Build System plugin. | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Christos Gourdoupis <xrigou> |
Component: | BuildSystem: Custom BuildSystems | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | apaku |
Priority: | NOR | ||
Version: | 4.2.60 | ||
Target Milestone: | 4.2.3 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christos Gourdoupis
2011-10-14 07:59:29 UTC
so you just run configure and that crashes kdev? @Andreas: can you take care of this please? I can't see any relevance to the custom buildsystem manager. The backtrace indicates that the only thing involved is the abstractfilemanager code doing some behind-the-scenes update or so. It really does sound as if this is a dupe of the mentioned report 260741 and the 'external change' is simply triggered by running whatever script is configured in the custom buildsystem manager as "Configure" tool. also, if it's simple to reproduce the following would be helpful: run kdevelop in valgrind and upload the log it creates: valgrind --track-origins=yes --num-callers=25 kdevelop &> log # reproduce crash # upload 'log' file I agree it is a dupe of 260741. My project is autotools based too, the only difference is I use the Custom Build System to configure it and build it. I was unable to trigger the crash while running under valgrind. It seems it happens only after some work is done. *** This bug has been marked as a duplicate of bug 260741 *** |