[llvm-bugs] [Bug 31756] New: XRay crashes when rtdscp access is disabled
via llvm-bugs
llvm-bugs at lists.llvm.org
Wed Jan 25 11:40:26 PST 2017
https://llvm.org/bugs/show_bug.cgi?id=31756
Bug ID: 31756
Summary: XRay crashes when rtdscp access is disabled
Product: XRay
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Runtime
Assignee: dberris at google.com
Reporter: simon.dardis at imgtec.com
CC: llvm-bugs at lists.llvm.org
Classification: Unclassified
Some Linux configurations inhibit the use of rtdscp, resulting in an illegal
instruction exception at runtime.
Furthermore, the expected files: /sys/devices/system/cpu/cpu0/tsc_freq_khz and
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq are not present.
Machine:
Linux mipstest 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02)
x86_64 GNU/Linux
Test output:
FAIL: XRay-x86_64-linux :: TestCases/Linux/argv0-log-file-name.cc (32456 of
38389)
******************** TEST 'XRay-x86_64-linux ::
TestCases/Linux/argv0-log-file-name.cc' FAILED ********************
Script:
--
/home/snd-local/releases/release/rc1/Phase3/Release/llvmCore-4.0.0-rc1.obj/./bin/clang
--driver-mode=g++ -fxray-instrument -m64 -std=c++11
/home/snd-local/releases/release/rc1/llvm.src/projects/compiler-rt/test/xray/TestCases/Linux/argv0-log-file-name.cc
-o
/home/snd-local/releases/release/rc1/Phase3/Release/llvmCore-4.0.0-rc1.obj/projects/compiler-rt/test/xray/X86_64LinuxConfig/TestCases/Linux/Output/argv0-log-file-name.cc.tmp
/home/snd-local/releases/release/rc1/Phase3/Release/llvmCore-4.0.0-rc1.obj/projects/compiler-rt/test/xray/X86_64LinuxConfig/TestCases/Linux/Output/argv0-log-file-name.cc.tmp
> xray.log.file.name 2>&1
ls | FileCheck xray.log.file.name
rm xray-log.* xray.log.file.name
--
Exit Code: 132
Command Output (stderr):
--
/home/snd-local/releases/release/rc1/Phase3/Release/llvmCore-4.0.0-rc1.obj/projects/compiler-rt/test/xray/X86_64LinuxConfig/TestCases/Linux/Output/argv0-log-file-name.cc.script:
line 4: 31143 Illegal instruction
/home/snd-local/releases/release/rc1/Phase3/Release/llvmCore-4.0.0-rc1.obj/projects/compiler-rt/test/xray/X86_64LinuxConfig/TestCases/Linux/Output/argv0-log-file-name.cc.tmp
> xray.log.file.name 2>&1
--
********************
Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80
FAIL: XRay-x86_64-linux :: TestCases/Linux/fixedsize-logging.cc (32458 of
38389)
******************** TEST 'XRay-x86_64-linux ::
TestCases/Linux/fixedsize-logging.cc' FAILED ********************
Script:
--
/home/snd-local/releases/release/rc1/Phase3/Release/llvmCore-4.0.0-rc1.obj/./bin/clang
--driver-mode=g++ -fxray-instrument -m64 -std=c++11
/home/snd-local/releases/release/rc1/llvm.src/projects/compiler-rt/test/xray/TestCases/Linux/fixedsize-logging.cc
-o
/home/snd-local/releases/release/rc1/Phase3/Release/llvmCore-4.0.0-rc1.obj/projects/compiler-rt/test/xray/X86_64LinuxConfig/TestCases/Linux/Output/fixedsize-logging.cc.tmp
XRAY_OPTIONS="verbosity=1 xray_logfile_base=fixedsize-logging-"
/home/snd-local/releases/release/rc1/Phase3/Release/llvmCore-4.0.0-rc1.obj/projects/compiler-rt/test/xray/X86_64LinuxConfig/TestCases/Linux/Output/fixedsize-logging.cc.tmp
2>&1 | FileCheck
/home/snd-local/releases/release/rc1/llvm.src/projects/compiler-rt/test/xray/TestCases/Linux/fixedsize-logging.cc
rm fixedsize-logging-*
--
Exit Code: 1
Command Output (stderr):
--
/home/snd-local/releases/release/rc1/llvm.src/projects/compiler-rt/test/xray/TestCases/Linux/fixedsize-logging.cc:19:12:
error: expected string not found in input
// CHECK: foo() is always instrumented!
^
<stdin>:2:1: note: scanning from here
==31182==Unable to determine CPU frequency for TSC accounting.
^
<stdin>:2:44: note: possible intended match here
==31182==Unable to determine CPU frequency for TSC accounting.
Ideally, XRay should probe if possible to determine if rtdsc(p) can be used.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170125/4ef4d6bb/attachment-0001.html>
More information about the llvm-bugs
mailing list