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 files in UTF16LE. The cmake
parser seems to not just read CMakeLists.txt and *.cmake, but also generally
all files with the extension .txt. Apparently the encoding of the example files
is handled correctly, but then the wide characters are given to the lexer that
expects chars, hence the one byte buffer overflow reported (just my guess,
didn't have a look at all the code involved).

If I delete all the UTF16 files, the whole code base is processed successfully.

So I guess the problem is kind of a duplicate of 363269, but more specific. The
cmake parser seems generally to greedy in selecting the files it processes.
Could that be narrowed down to only CMakeLists.txt and *.cmake?

Feel free to close this one if you think it's covered by 363269.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to