search for: xray_mod

...oduced by GHC. Getting the basics working is not too complicated after adding the right function attribute but any analysis shows the 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 fu...

Hi all, I want to test X-ray performance and compare it with other research tools, so I use Clang 7.0.0 to compile and instrument GNU binutils-2.3.1 with the following commands: cd binutils-2.31/ mkdir build cd build/ CC=$local/clang CXX=$local/clang++ CFLAGS=-fxray-instrument CXXFLAGS=-fxray-instrument ../configure --prefix=/home/zhangysh1995/local make Then I extract instrumentation map

Hi All, I am trying to test run clang XRay tool. I was following the steps at [1]. But the log file does not seem to get generated. According to the instructions I used 'fxray-instrument' switch when compiling and then specified 'patch_premain=true' at XRAY_OPTIONS. Is there anything else that I need to do? I am on a trunk build of clang. Could that be it? I am on clang version

...behavior mentioned above by displaying the result from the test file and then the result from modifying the fdr-mode.cc test provided in the TestCases/Posix directory. ====UNMODIFIED fdr-mode.cc==== ./clang++ -fxray-instrument fdr-mode.cc -o fdr-mode XRAY_OPTIONS="patch_premain=false xray_mode=xray-fdr verbosity=1" XRAY_FDR_OPTIONS="func_duration_thr eshold_us=0" ./fdr-mode Logging before init. ==31756==Initializing FDR mode with options: buffer_size=16384:buffer_max=10 ==31756==XRay FDR init successful. Init status 2 Patching... Joined Finalize status 4 Main exec...

...omplicated after adding the right function >> attribute but any analysis shows the 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...

...>> attribute but any analysis shows the 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...

...Size VMA LMA File off Algn 27 xray_instr_map 00000100 0000000000637ac0 0000000000637ac0 00037ac0 2**0 CONTENTS, ALLOC, LOAD, DATA 3. Then I use command "XRAY_OPTIONS="patch_premain=true xray_mode=xray-basic verbosity=2" ./matrix " to generate log file, which works perfectly: ==22294==XRay: Log file in 'xray-log.matrix.G42i0m' Enter rows and column for first matrix: 1 1 Enter rows and column for second matrix: 1 1...

...break; } } return 0; } I compiled the test file using clang 7.0 and ran it: ================= ./clang++ -fxray-instrument test.cpp –o test XRAY_OPTIONS="patch_premain=true xray_mode=xray-basic verbosity=1" ./test The output shows that logger prints out the parent TID 11 times, but making the gettid syscall in the test shows that the TIDs of the children are different than their parent process. Here is the output: ================= ==24020==XRay: Log file in '...