239
Listing 12-30 shows the same code run with Persistence Inspector, which also reports
“Overlapping regions registered in different transactions” in diagnostic 25. The first 24
diagnostic results were related to stores not added to our transactions corresponding
with the locking and unlocking of our volatile mutex; these can be ignored.
Listing 12-30. Generating a report with Intel Inspector – Persistence Inspector
for code Listing 12-28
$ pmeminsp rp -- ./listing_12-28
...
#=============================================================
# Diagnostic # 25: Overlapping regions registered in different transactions
#------------------transaction
in /data/listing_12-28!main at listing_12-28.c:69 - 0xEB6
in /lib64/libc.so.6!__libc_start_main at :
- 0x223D3
in /data/listing_12-28!_start at : - 0xB44
protects
memory region
in /data/listing_12-28!main at listing_12-28.c:73 - 0xF1F
in /lib64/libc.so.6!__libc_start_main at :
- 0x223D3
in /data/listing_12-28!_start at : - 0xB44
overlaps with
memory region
in /data/listing_12-28!func at listing_12-28.c:55 - 0xDA8
in /lib64/libpthread.so.0!start_thread at :
- 0x7DCD
in /lib64/libc.so.6!__clone at : - 0xFDEAB
Analysis complete. 25 diagnostic(s) reported.
Chapter 12 Debugging persistent MeMory appliCations