You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Detected a hypervisor/virtualization technology. Some metrics might not be available due to configuration or availability of virtual hardware features.
===== Processor information =====
Linux arch_perfmon flag : yes
Hybrid processor : no
IBRS and IBPB supported : yes
STIBP supported : yes
Spec arch caps supported : yes
Max CPUID level : 32
CPU family : 6
CPU model number : 183
pcm: /usr/src/packages/BUILD/src/types.h:1561: pcm::uint32 pcm::build_bit_ui(pcm::uint32, pcm::uint32): Assertion `end <= 31' failed.
DEBUG: caught signal to interrupt (Aborted).**
What can I do to solve the bug?
The text was updated successfully, but these errors were encountered:
Hi, thanks for reporting the issue. Unfortunately it is not reproducible in our VMWare environment. Would it be possible to compile pcm in debug mode (sh scripts/debug-build.sh) and then run "gdb ./pcm" and then "run", then "bt" to show the assert callstack. This should be helpful to understand what is going on.
Hello developers, when I build the code in a Ubuntu 18.04 virtual machine and run, there is one question troubled me for a long time.
**yang@Pluto:~$ pcm
Intel(r) Performance Counter Monitor (2024-11-05 15:03:02 +0100 ID=a83f3125)
Detected a hypervisor/virtualization technology. Some metrics might not be available due to configuration or availability of virtual hardware features.
===== Processor information =====
Linux arch_perfmon flag : yes
Hybrid processor : no
IBRS and IBPB supported : yes
STIBP supported : yes
Spec arch caps supported : yes
Max CPUID level : 32
CPU family : 6
CPU model number : 183
pcm: /usr/src/packages/BUILD/src/types.h:1561: pcm::uint32 pcm::build_bit_ui(pcm::uint32, pcm::uint32): Assertion `end <= 31' failed.
DEBUG: caught signal to interrupt (Aborted).**
What can I do to solve the bug?
The text was updated successfully, but these errors were encountered: