## Issues in compatibility reports

After Compatibility Analyser has run the analysis, the generated reports are listed in the application's view. Some items are reported differently, depending on whether the report is for header or library files.

On the report, you can also view the OK cases that did not have compatibility problems.

### Reading the report

The first part of the report lists general information such as the creation date, the baseline and current versions, and the parameters used. See the following example:

The second part contains the BC breaks that were found. For each header file with problems, the baseline header file and the matching current header file are listed. Below them, the changes that may affect the BC are listed. Each issue contains:

- a description of the problem,
- the cause, and
- the level of severity: BBC Break, Possible BBC Break or Informative. For example:

For libraries, each issue contains:

- the type of change (added, modified, deleted),
- where it occurred,
- details, and
- the level of severity: BBC Break, Possible BBC Break or Informative. For example:

### Analysing the findings

- Informative items are reported to help the analyst and do not as such constitute a BC break.
- Items marked as BBC Break or Possible BBC Break need to be analyzed to determine whether they are breaks or not. Some of the breaks come from the platform and some are introduced by the product.

To ease the analysis of the report, make sure that you have the report generated for the platform release the product is based on, as well as a list of known issues (see Configuring the knownissues.xml file) in the platform. For each break (or possible break) in the product, the report for the platform is then checked.

- If the break is also in the platform, you can check the list of known issues and see whether it is a real BC break.
- If the break is not a known break in the platform, it has usually been introduced by the product. In this case, consult a binary compatibility expert who can carry out further analysis.

##### Related references

- Reported Binary Compatibility issues
- Reported library analysis issues

##### Related tasks

- Viewing the reports