search for: hgd9oi

...function names but not the locations of the functions. In particular, I run a program which has been instrumented as follows: XRAY_OPTIONS="patch_premain=true xray_mode=xray-basic verbosity=1" ./llvm which then writes out an xray-log file. ==4193==XRay: Log file in 'xray-log.llvm.hgD9oi' ==4193==Cleaned up log for TID: 4193 I then attempt to use the xray-account utility to analyse the log but whilst the functions are named, the locations of the functions are displayed as <invalid>:0:0:. > llvm-xray account -sort=sum -sortorder=dsc -instr_map ./llvm xray-log.llvm.h...

...t; In particular, I run a program which has been instrumented as follows: >> >> XRAY_OPTIONS="patch_premain=true xray_mode=xray-basic verbosity=1" ./llvm >> >> which then writes out an xray-log file. >> >> ==4193==XRay: Log file in 'xray-log.llvm.hgD9oi' >> ==4193==Cleaned up log for TID: 4193 >> >> I then attempt to use the xray-account utility to analyse the log but >> whilst the functions are named, the locations of the functions are >> displayed as <invalid>:0:0:. >> >>> llvm-xray accoun...

...strumented as follows: >> >> >> >> XRAY_OPTIONS="patch_premain=true xray_mode=xray-basic verbosity=1" ./llvm >> >> >> >> which then writes out an xray-log file. >> >> >> >> ==4193==XRay: Log file in 'xray-log.llvm.hgD9oi' >> >> ==4193==Cleaned up log for TID: 4193 >> >> >> >> I then attempt to use the xray-account utility to analyse the log but >> >> whilst the functions are named, the locations of the functions are >> >> displayed as <invalid>:0...