Resolved Issues

DTS2025082901780

[Affinity Analyzer] [memtrace analysis] [Backend] When layer 0 of the call stack is a system library file (such as an SO file) and other layers contain valid service or code information, this type of race is incorrectly filtered out. As a result, some information is missing.

Minor

Take the following mitigation measures:

• When the call stack check function is enabled and the dr-check command is used to analyze and report ELF files, the dr-check command processes each detected race and the call stack information of the two accesses.
  • If layer 0 of the call stack is located in the SO system library but valid information related to the target ELF file exists at another layer, file information corresponding to that layer is extracted, the race record is retained, and the race record is allowed to participate in a subsequent race filtering, deduplication, and source code mapping processing.
  • If layer 0 of the call stack is located in the SO system library while other layers are also system libraries or third-party library files and do not contain user code, the race record is invalid and filtered out.

  This ensures that the miss rate of race conditions is effectively reduced when call stack check is enabled.

• During the dr-check process, retain the original check report generated by memtracer and describe the report usage in the documentation.

When a large number of system functions are involved, dr-check processes only layer 0 of the call stack. As a result, some real races are incorrectly filtered out, causing misses.

The intermediate result report generated by memtracer is retained in dr-check test results, and the report usage is added to the documentation for reference.