Bükki Dániel

I have identified two major issues that contribute to the failure of incremental parsing: **[1]** The segmentation fault comes from `CppMetricsParser::CppMetricsParser` during plugin creation: https://github.com/Ericsson/CodeCompass/blob/8e84d84e29a0cec6cb0af9f6dcc587ea9ff34480/plugins/cpp_metrics/parser/src/cppmetricsparser.cpp#L47 `node->location.file` has not been not...

### Current state Depending on the kind of `CppEntity` being parsed, declarations and instantiations/calls may or may not persist additional (duplicate) entities for the relevant pieces of code into the...

### Assumptions on correctness In `VisitRecordDecl`, just before the creation of the `CppRecord` structure that will later be persisted, there is the following check: ``` if (!rd_->isThisDeclarationADefinition()) return true; ```...

The above statistics were exported from my diagnostics branch created specifically for this purpose: https://github.com/dbukki/CodeCompass/tree/diagnostics _Note: The changes on this branch are meant to serve diagnostic purposes of hypothetical scenarios...

For reference, here is a list of McCabe and bumpy road metrics exported from the Xerces-C project using the current state: [xerces-bumpyroad.log](https://github.com/Ericsson/CodeCompass/files/14449164/xerces-bumpyroad.log) [xerces-mccabe.log](https://github.com/Ericsson/CodeCompass/files/14449172/xerces-mccabe.log)

I found an interesting phenomenon in the parser: In C++, we know that records and functions can be either just a declaration or an actual definition. However, our policy towards...

> If I execute incremental parsing on a project, parsing fails immediately with a segmentation fault. @dbukki can you please check if this is coming from your modifications? I checked...