Plist Output CSA 'type' field missing

[schrc3b6]

Hi,

I'm currently switching from scan-build to CodeChecker, great tool btw :) However, I'm noticing that 'type' field from the plist reports the CSA generates is missing in the final plist reports. Is there a reason for removing this field? I'm currently using the error-type field in post-processing.

Thanks

[whisperity]

Could you please show a small example of what this field may contain? It is very well possible that the output format of CSA changed and we did not pick up on this fact.

[schrc3b6]

The CSA provides for example the following fields:

   <key>description</key><string>Potential leak of memory pointed to by &apos;newItem&apos;</string>
   <key>category</key><string>Memory error</string>
   <key>type</key><string>Memory leak</string>
   <key>check_name</key><string>unix.Malloc</string>

The created by codechecker is missing the type field:

            <key>category</key>
            <string>Memory error</string>
            <key>check_name</key>
            <string>unix.Malloc</string>
            <key>description</key>
            <string>Potential leak of memory pointed to by 'newItem'</string>

Here is another example: CSA:

   <key>description</key><string>Use of memory after it is freed</string>
   <key>category</key><string>Memory error</string>
   <key>type</key><string>Use-after-free</string>
   <key>check_name</key><string>unix.Malloc</string>

CodeChecker:

            <key>category</key>
            <string>Memory error</string>
            <key>check_name</key>
            <string>unix.Malloc</string>
            <key>description</key>
            <string>Use of memory after it is freed</string>

The type field contains the error type. Which I use in post-processing to extend error messages and modify the severity. Since a single checker provides multiple error types, as seen above, is relying on the check_name suboptimal.