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

            Bug ID: 392336
           Summary: libclang crashes on C++ project and kdevelop follows
                    with double free or curruption
           Product: kdevelop
           Version: 5.2.1
          Platform: Fedora RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Language Support: CPP (Clang-based)
          Assignee: kdevelop-bugs-n...@kde.org
          Reporter: kde-b...@ctacke.de
  Target Milestone: ---

Created attachment 111651
  --> https://bugs.kde.org/attachment.cgi?id=111651&action=edit
console output on the crash.

I have an annoying Crash on C++ project. I have Kdevelop 5.2.1 running on my
Fedora machine from the repos and also in a VM as AppImage on Ubuntu 16.04 and
both crash when indexing/parsing the source.

The project is https://github.com/riebl/vanetza on commit
c33b7f6c9d5bed49a5dfbb948963a9895a144129.
As soon as I add the project to a kdevelop session its being indexed and at
some point inevitably crashes before finishing the parsing.

First I get the output from a libclang crash and the I get either "double free
or corruption (!prev)" or "corrupted double linked list". I have the full
commandline output of the first one appended.


libclang: crash detected during parsing: {
  'source_filename' : '<arbitrary
path>/vanetza/vanetza/geonet/data_request.cpp'
  'command_line_args' : ['clang', '-ferror-limit=100', '-fspell-checking', '',
'-Wunused-parameter', '-Wunreachable-code', '-Wall', '-std=c++11', '-nostdinc',
'-nostdinc++', '-xc++', '-isystem/usr/include/c++/7',
'-isystem/usr/include/c++/7/x86_64-redhat-linux',
'-isystem/usr/include/c++/7/backward', '-isystem/usr/local/include',
'-isystem/usr/lib64/clang/4.0.1/include', '-isystem/usr/include', '-imacros',
'/tmp/kdevelop.rA5119'],
  'unsaved_files' : [],
  'options' : 781,
}

I really like KDevelop and use it for all my cmake related proejcts and most
other in regard to C/C++.

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

Reply via email to