https://bugs.kde.org/show_bug.cgi?id=392336
--- Comment #4 from christian tacke <kde-b...@ctacke.de> --- Hi Millian, thank you for the clarification. If KDevelops stack / memory is corrupted there's nothing to be done. I understand. I ran the commands on another system with clang 3.8 and there it did not crash. Though this does not say anything. But with your guess that it behaves differently when called from kdevelop, I would like to try creating a minimal example for the clang people which does not involve kdevelop if possible. Can you point me to the source where the parsing is triggered? The system I tested it on and could produce the crash logs runs a 4.0 clang. I'll test it there too. -- You are receiving this mail because: You are watching all bug changes.
