The report generated by Freja points the user to the source code lines containing the memory accesses that cause each issue, as described above. However, a single source code line may contain complex expressions that contain many memory references, and it may not be obvious which one of these it is that is causing the issue.

To make it easier for the user to determine which memory accesses or data structure in a large expression is causing an issue, the report also displays the previous location at which that particular memory location was written. Usually only one variable is written on each line, which directly tells the programmer which variable in the original expression is involved in the issue.