Hi, I have a question regarding the "definitely lost" leaks. What is the "loss record" and does the whole report have a single sequence of "loss record"? If you look at the following segments from the report. The 2nd and 3rd both are from "loss record 21". However, the PID is different. I'm wondering if they're one leak reported twice, or 2 instances of a leak happening at different times (and in different processes)? Any help would be appreciated.
-Wayne ==4933== 8 bytes in 1 blocks are definitely lost in loss record 25 of 150 ==4933== at 0x40046CE: malloc (vg_replace_malloc.c:149) ==4933== by 0x6872631: cmi_parse_response (cmi.c:166) ==4933== by 0x69A4FCE: sanos_variable_configuration_get (cli_variable.c:680) ==4933== by 0x68CDCB3: vsh_procket_init (clic_main.cc:2314) ==4933== by 0x670ED58: SC_Initialize_vshell (in /isan/plugin/0/isan/lib/libsam_coupler.so.0.0.0) ==6266== 8 bytes in 1 blocks are definitely lost in loss record 21 of 221 ==6266== at 0x40046CE: malloc (vg_replace_malloc.c:149) ==6266== by 0x6872631: cmi_parse_response (cmi.c:166) ==6266== by 0x69A4FCE: sanos_variable_configuration_get (cli_variable.c:680) ==6266== by 0x68CDCB3: vsh_procket_init (clic_main.cc:2314) ==6266== by 0x670ED58: SC_Initialize_vshell (in /isan/plugin/0/isan/lib/libsam_coupler.so.0.0.0) ==6331== 8 bytes in 1 blocks are definitely lost in loss record 21 of 221 ==6331== at 0x40046CE: malloc (vg_replace_malloc.c:149) ==6331== by 0x6872631: cmi_parse_response (cmi.c:166) ==6331== by 0x69A4FCE: sanos_variable_configuration_get (cli_variable.c:680) ==6331== by 0x68CDCB3: vsh_procket_init (clic_main.cc:2314) ==6331== by 0x670ED58: SC_Initialize_vshell (in /isan/plugin/0/isan/lib/libsam_coupler.so.0.0.0) ==6358== 8 bytes in 1 blocks are definitely lost in loss record 21 of 225 ==6358== at 0x40046CE: malloc (vg_replace_malloc.c:149) ==6358== by 0x6872631: cmi_parse_response (cmi.c:166) ==6358== by 0x69A4FCE: sanos_variable_configuration_get (cli_variable.c:680) ==6358== by 0x68CDCB3: vsh_procket_init (clic_main.cc:2314) ==6358== by 0x670ED58: SC_Initialize_vshell (in /isan/plugin/0/isan/lib/libsa ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
