*** glibc detected *** /opt/intel/itac/8.0.1.009/bin/traceanalyzer.bin: malloc(): memory corruption: 0x00007fdfa0022ad0 ***

*** glibc detected *** /opt/intel/itac/8.0.1.009/bin/traceanalyzer.bin: malloc(): memory corruption: 0x00007fdfa0022ad0 ***

Hello,

After a rather lenghty discussion [http://software.intel.com/en-us/forums/showthread.php?t=82155], I was able to generate a trace of an application I wanted to profile. Now I have trouble analyzing the trace I managed to generate.

When I try to run the trace analyzer, I get the following error:

##### [09:09:28] # [dare2be@schroedinger:~/Praca/IPJ/SuperBayes-v1.5] #####
$ traceanalyzer superbayes_multinest.stf
*** glibc detected *** /opt/intel/itac/8.0.1.009/bin/traceanalyzer.bin: malloc(): memory corruption: 0x00007f7684011710 ***
*** glibc detected *** /opt/intel/itac/8.0.1.009/bin/traceanalyzer.bin: malloc(): memory corruption: 0x00007f7678010ba0 ***
*** glibc detected *** /opt/intel/itac/8.0.1.009/bin/traceanalyzer.bin: malloc(): memory corruption: 0x00007f7680001140 ***
*** glibc detected *** /opt/intel/itac/8.0.1.009/bin/traceanalyzer.bin: malloc(): memory corruption: 0x00007f767c01c520 ***
^C

This occurs the moment I try to zoom in - the application freezes and there are above errors on the console.

I attach output of valgrind run on the traceanalyzer, coming from the following command:

##### [09:05:59] # [dare2be@schroedinger:~/Praca/IPJ/SuperBayes-v1.5] #####
$  valgrind --error-limit=no --log-file=log.valgrind --trace-children=yes --tool=memcheck  /opt/intel/itac/8.0.1.009/bin/traceanalyzer superbayes_multinest.stf

Worth noting is the fact that running the application through valgrind caused it not to crash with glibc errors.

I am using the Intel Trace Analyzer 8.0 Update 1, as shown in the "About ..." dialog.

I also attach the trace files, for your evaluation.

AnexoTamanho
Download log.valgrind1.42 MB
Download trace.tgz392.51 KB
2 posts / novo 0
Último post
Para obter mais informações sobre otimizações de compiladores, consulte Aviso sobre otimizações.

Hi,

I was able to reproduce this error and it looks like an issue of the traceanalyzer. We will investigate it. Right now unfortunately I even cannot suggest any workaround.

Regards!
Dmitry

Deixar um comentário

Faça login para adicionar um comentário. Não é membro? Inscreva-se hoje mesmo!