[kdevelop] [Bug 367841] Crash during parsing of cmake/C++/Python files

2016-09-08 Thread Kevin Funk via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367841 Kevin Funk changed: What|Removed |Added Resolution|--- |DUPLICATE

[kdevelop] [Bug 367841] Crash during parsing of cmake/C++/Python files

2016-09-08 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367841 --- Comment #8 from axel.kellerm...@gmx.de --- I found the problem, and it's actually similar, but not the same as bug 363269. The code base being parsed contains a subfolder with example text in a couple of different asian languages, all stored as .txt

[kdevelop] [Bug 367841] Crash during parsing of cmake/C++/Python files

2016-09-08 Thread Kevin Funk via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367841 --- Comment #7 from Kevin Funk --- Could that be related to bug 363269? Could you check the CMake file KDevelop is parsing (see debug output). Is it a binary file? -- You are receiving this mail because: You are watching all bug

[kdevelop] [Bug 367841] Crash during parsing of cmake/C++/Python files

2016-09-08 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367841 --- Comment #6 from axel.kellerm...@gmx.de --- Created attachment 100989 --> https://bugs.kde.org/attachment.cgi?id=100989=edit ASAN output of heap-buffer-overflow error during parsing of CMake file -- You are receiving this mail because: You are

[kdevelop] [Bug 367841] Crash during parsing of cmake/C++/Python files

2016-09-08 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367841 --- Comment #5 from axel.kellerm...@gmx.de --- I compiled kdevelop and kdevplatform with ASAN and tested again on two platforms: 1. A laptop with only 4GB of RAM, where memory actually is kind of an issue. kdevelop takes up ~3.5GB of RAM and the

[kdevelop] [Bug 367841] Crash during parsing of cmake/C++/Python files

2016-09-01 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367841 --- Comment #2 from axel.kellerm...@gmx.de --- And another one: #0 0x00300147e4f5 in malloc_consolidate (av=av@entry=0x7fffa420) at malloc.c:4184 #1 0x00300148155e in _int_malloc (av=av@entry=0x7fffa420, bytes=bytes@entry=19684) at

[kdevelop] [Bug 367841] Crash during parsing of cmake/C++/Python files

2016-09-01 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367841 --- Comment #3 from axel.kellerm...@gmx.de --- I'd be happy to help with debugging, but I need some pointers where to start, and what to look for. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 367841] Crash during parsing of cmake/C++/Python files

2016-09-01 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367841 axel.kellerm...@gmx.de changed: What|Removed |Added Summary|Crash during parsing of |Crash during parsing of