https://bugs.kde.org/show_bug.cgi?id=374234

            Bug ID: 374234
           Summary: KDevelop freezed when parsing llvm+clang source code
           Product: kdevelop
           Version: git master
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Language Support: CPP (Clang-based)
          Assignee: kdevelop-bugs-n...@kde.org
          Reporter: xiangzha...@gmail.com
  Target Milestone: ---

Hi KDevelop developers,

When I Open/Import LLVM projects and clicked the QTreeView
llvm/tools/clang/lib/StaticAnalyzer/Checkers, KDevelop freezed!

There are 4 threads involved in parsing the huge LLVM projects, and htop to see
CPU is 100, and command line show libclang error such as:

libclang: crash detected during parsing: {
  'source_filename' :
'/data/project/LLVM/llvm/tools/clang/test/Driver/rewrite-map-in-diagnostics.c'
  'command_line_args' : ['clang', '-ferror-limit=100', '-fspell-checking',
'-Wdocumentation', '-Wunused-parameter', '-Wunreachable-code', '-Wall',
'-std=c99', '-nostdinc', '-xc', '-isystem/usr/local/include',
'-isystem/usr/lib/clang/3.9.1/include', '-isystem/usr/include', '-imacros',
'/tmp/kdevelop.JZ7809'],
  'unsaved_files' :
[('/data/project/LLVM-China/tartan/clang-plugin/plugin.cpp', '...', 12414),
('/data/project/LLVM/llvm/tools/clang/lib/StaticAnalyzer/Checkers/SimpleStreamChecker.cpp',
'...', 9378),
('/data/project/LLVM/llvm/tools/clang/lib/StaticAnalyzer/Checkers/MallocChecker.cpp',
'...', 102293),
('/data/project/LLVM-China/tartan/clang-plugin/gerror-checker.h', '...', 7494),
('/data/project/LLVM-China/tartan/clang-plugin/gerror-checker.cpp', '...',
40442)],
  'options' : 557,
}
clang_parseTranslationUnit2 return with error code 2
  (start KDevelop with `KDEV_CLANG_DISPLAY_DIAGS=1 kdevelop` to see more
diagnostics)
Failed to parse translation unit:
"/data/project/LLVM/llvm/tools/clang/test/Driver/rewrite-map-in-diagnostics.c"

Regards,
Leslie Zhai

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

Reply via email to