[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 --- Comment #13 from RJVB --- Created attachment 96640 --> https://bugs.kde.org/attachment.cgi?id=96640=edit [OS X] valgrind --track-origins=yes --smc-check=all-non-file --error-limit=no kdevelop5 -- You are receiving this mail

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 --- Comment #14 from RJVB --- Created attachment 96641 --> https://bugs.kde.org/attachment.cgi?id=96641=edit [OS X] valgrind --track-origins=yes --smc-check=all-non-file --error-limit=no kdevelop5 -- You are receiving this mail

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 --- Comment #10 from RJVB --- I've got the log, but a priori it just shows a crash while dlopen'ing kdevclangsupport without any further explanation as to what the gdb backtrace above already shows. I rebuilt kdevclangsupport

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 --- Comment #11 from Kevin Funk --- For the record: Distro-provided Clang/LLVM works fine for me on Ubuntu Wily. I'm sure I tried both the 3.6 and 3.7 versions at some point, without problems. -- You are receiving this mail because:

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 --- Comment #12 from RJVB --- (In reply to Kevin Funk from comment #11) > For the record: Distro-provided Clang/LLVM works fine for me on Ubuntu Wily. The crash I saw with Ubuntu's Clang 3.6 was different from the one I saw with

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 --- Comment #8 from RJVB --- Created attachment 96525 --> https://bugs.kde.org/attachment.cgi?id=96525=edit valgrind --track-origins=yes -v --error-limit=no kdevelop5 (against llvm 3.7) -- You are receiving this mail because:

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 --- Comment #9 from Milian Wolff --- please rerun without -v but with --smc-check=all-non-file -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 --- Comment #5 from Milian Wolff --- please use valgrind to find out whats going on instead of guessing. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 Kevin Funk changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC|

[kdevelop] [Bug 357630] crash when exiting with parser running [KDevelop::BackgroundParser::~BackgroundParser]

https://bugs.kde.org/show_bug.cgi?id=357630 --- Comment #2 from RJVB --- Yeah, maybe when I am sure I can reproduce it, and preferably under Linux. Valgrind'ing CPU & memory-hungry processes has been a very efficient way to get KPs on OS X for me so I tend to avoid it. --