Beta for Linux* 2017 - runsa.options: second, empty, --event-config line

[jindrich_k_]

when i try to run memory analysis, "the result you are opening does not contain any data".

taking to the command line:

/opt/intel/vtune_amplifier_xe_2017.0.0.457868/bin64/amplxe-cl -collect memory-access -app-working-dir /home/kook/ClionProjects/t2 -- /home/kook/ClionProjects/t2/cppout silent

i get:

amplxe: Error: Option 'event-config' received value from the next argument: '--sample-after-multiplier=1.0', but it seems to be an option. Use '-option=value' declaration form or make sure that value is not missed

the generated runsa.options file looks like this:

-r
/home/kook/intel/amplxe/projects/cccc/r001macc
--target=host
--itt-config=frame
--bandwidth-limits
--data-limit-mb=500
--mrte-type=java
--event-config=CPU_CLK_UNHALTED.CORE:sa=2300000,CPU_CLK_UNHALTED.REF:sa=2300000,INST_RETIRED.ANY:sa=
2300000,BUS_DRDY_CLOCKS.THIS_AGENT:sa=100003,BUS_TRANS_BURST.SELF:sa=200003
--event-config
--sample-after-multiplier=1.0
--event-mux
--mrte-mode=auto
--
/home/kook/ClionProjects/t2/cppout
silent

notice the spurious --event-config line. I wasnt able to get rid of it with any switches in the gui.

[Dmitry_R_Intel1]

Hello,

Could you please provide the processor name for your system?

[jindrich_k_]

hi

cat /proc/cpuinfo
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 23
model name    : Pentium(R) Dual-Core CPU       T4500  @ 2.30GHz
stepping    : 10
microcode    : 0xa0b
cpu MHz        : 1200.000
cache size    : 1024 KB
physical id    : 0
siblings    : 2
core id        : 0
cpu cores    : 2
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 13
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm dtherm

...

[Dmitry_R_Intel1]

The problem described in this thread is specific for old Core 2 processors. If possible please try running analysis on a newer platform - Sandy Bridge based or later. You should not see such issues there.