sstsimulator / sst-dumpi Goto Github PK

Clang leak sanitizer flags a bunch of leaks in dumpi2dumpi and dumpi2ascii. E.g.:

==235223==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 96 byte(s) in 1 object(s) allocated from:
#0 0x40f2ce in calloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:76
#1 0x7f4b1b792a51 in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:431:28
#2 0x430a3e in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2ascii.c:90:17
#3 0x7f4b1a87f3d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 65 byte(s) in 1 object(s) allocated from:
#0 0x40f166 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f4b1b790eeb in dumpi_build_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/types.c:106:29
#2 0x7f4b1b781bde in undumpi_read_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:83:26
#3 0x430a58 in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2ascii.c:94:26
#4 0x7f4b1a87f3d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 26 byte(s) in 1 object(s) allocated from:
#0 0x40f166 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f4b1b79195e in get_string /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/iodefs.h:482:18
#2 0x7f4b1b7916e6 in dumpi_read_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:107:25
#3 0x7f4b1b792b4d in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:506:5
#4 0x430a3e in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2ascii.c:90:17
#5 0x7f4b1a87f3d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 16 byte(s) in 1 object(s) allocated from:
#0 0x40f2ce in calloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:76
#1 0x7f4b1b7aab8b in dumpi_read_init /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/dumpiio.c:2559:25
#2 0x7f4b1b787c50 in libundumpi_grab_init /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/bindings.c:2241:3
#3 0x7f4b1b781c68 in undumpi_read_single_call /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:116:5
#4 0x7f4b1b781e4f in undumpi_read_stream_full /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:179:9
#5 0x7f4b1b781d44 in undumpi_read_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:134:10
#6 0x430abe in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2ascii.c:104:5
#7 0x7f4b1a87f3d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 9 byte(s) in 1 object(s) allocated from:
#0 0x40f166 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f4b1b790ec1 in dumpi_build_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/types.c:100:18
#2 0x7f4b1b781bde in undumpi_read_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:83:26
#3 0x430a58 in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2ascii.c:94:26
#4 0x7f4b1a87f3d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x40f166 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f4b1b79195e in get_string /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/iodefs.h:482:18
#2 0x7f4b1b7916f2 in dumpi_read_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:108:25
#3 0x7f4b1b792b4d in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:506:5
#4 0x430a3e in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2ascii.c:90:17
#5 0x7f4b1a87f3d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

SUMMARY: LeakSanitizer: 220 byte(s) leaked in 6 allocation(s).
Files ttrace.txt and /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/../../tests/traces/testtrace-0000.txt differ
FAIL test_dumpi2ascii.sh (exit status: 1)

=================================================================
==235247==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 100 byte(s) in 2 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f9f4e4ac0c9 in __GI___strdup (/lib64/libc.so.6+0x8c0c9)

Direct leak of 96 byte(s) in 1 object(s) allocated from:
#0 0x41160e in calloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:76
#1 0x7f9f4f355a51 in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:431:28
#2 0x441b21 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:743:28
#3 0x432e9f in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:85:13
#4 0x7f9f4e4423d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 65 byte(s) in 1 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f9f4f353eeb in dumpi_build_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/types.c:106:29
#2 0x441bb9 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:771:28
#3 0x432e9f in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:85:13
#4 0x7f9f4e4423d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 26 byte(s) in 1 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f9f4f35495e in get_string /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/iodefs.h:482:18
#2 0x7f9f4f3546e6 in dumpi_read_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:107:25
#3 0x7f9f4f355b4d in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:506:5
#4 0x441b21 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:743:28
#5 0x432e9f in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:85:13
#6 0x7f9f4e4423d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 16 byte(s) in 1 object(s) allocated from:
#0 0x41160e in calloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:76
#1 0x7f9f4f36db8b in dumpi_read_init /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/dumpiio.c:2559:25
#2 0x7f9f4f34ac50 in libundumpi_grab_init /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/bindings.c:2241:3
#3 0x7f9f4f344c68 in undumpi_read_single_call /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:116:5
#4 0x7f9f4f344e4f in undumpi_read_stream_full /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:179:9
#5 0x7f9f4f344d44 in undumpi_read_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:134:10
#6 0x441ba8 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:765:12
#7 0x432e9f in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:85:13
#8 0x7f9f4e4423d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f9f4f35495e in get_string /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/iodefs.h:482:18
#2 0x7f9f4f3546f2 in dumpi_read_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:108:25
#3 0x7f9f4f355b4d in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:506:5
#4 0x441b21 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:743:28
#5 0x432e9f in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:85:13
#6 0x7f9f4e4423d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Indirect leak of 9 byte(s) in 1 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f9f4f353ec1 in dumpi_build_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/types.c:100:18
#2 0x441bb9 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:771:28
#3 0x432e9f in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:85:13
#4 0x7f9f4e4423d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

SUMMARY: LeakSanitizer: 320 byte(s) leaked in 8 allocation(s).

=================================================================
==235281==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 384 byte(s) in 4 object(s) allocated from:
#0 0x41160e in calloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:76
#1 0x7fc662f03a51 in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:431:28
#2 0x441b21 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:743:28
#3 0x432e49 in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:77:19
#4 0x7fc661ff03d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 260 byte(s) in 4 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7fc662f01eeb in dumpi_build_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/types.c:106:29
#2 0x441bb9 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:771:28
#3 0x432e49 in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:77:19
#4 0x7fc661ff03d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 242 byte(s) in 6 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7fc66205a0c9 in __GI___strdup (/lib64/libc.so.6+0x8c0c9)

Direct leak of 136 byte(s) in 1 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x432df4 in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:67:21
#2 0x7fc661ff03d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 104 byte(s) in 4 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7fc662f0295e in get_string /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/iodefs.h:482:18
#2 0x7fc662f026e6 in dumpi_read_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:107:25
#3 0x7fc662f03b4d in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:506:5
#4 0x441b21 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:743:28
#5 0x432e49 in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:77:19
#6 0x7fc661ff03d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 64 byte(s) in 4 object(s) allocated from:
#0 0x41160e in calloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:76
#1 0x7fc662f1bb8b in dumpi_read_init /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/dumpiio.c:2559:25
#2 0x7fc662ef8c50 in libundumpi_grab_init /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/bindings.c:2241:3
#3 0x7fc662ef2c68 in undumpi_read_single_call /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:116:5
#4 0x7fc662ef2e4f in undumpi_read_stream_full /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:179:9
#5 0x7fc662ef2d44 in undumpi_read_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/libundumpi/libundumpi.c:134:10
#6 0x441ba8 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:765:12
#7 0x432e49 in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:77:19
#8 0x7fc661ff03d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 32 byte(s) in 4 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7fc662f0295e in get_string /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/iodefs.h:482:18
#2 0x7fc662f026f2 in dumpi_read_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:108:25
#3 0x7fc662f03b4d in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:506:5
#4 0x441b21 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:743:28
#5 0x432e49 in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:77:19
#6 0x7fc661ff03d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Indirect leak of 36 byte(s) in 4 object(s) allocated from:
#0 0x4114a6 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7fc662f01ec1 in dumpi_build_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/types.c:100:18
#2 0x441bb9 in d2d_parse_stream /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi-callbacks.c:771:28
#3 0x432e49 in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2dumpi.c:77:19
#4 0x7fc661ff03d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

SUMMARY: LeakSanitizer: 1258 byte(s) leaked in 31 allocation(s).

==235316==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 96 byte(s) in 1 object(s) allocated from:
#0 0x40f2ce in calloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:76
#1 0x7f16f1b42a51 in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:431:28
#2 0x430a3e in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2ascii.c:90:17
#3 0x7f16f0c2f3d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 26 byte(s) in 1 object(s) allocated from:
#0 0x40f166 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f16f1b4195e in get_string /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/iodefs.h:482:18
#2 0x7f16f1b416e6 in dumpi_read_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:107:25
#3 0x7f16f1b42b4d in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:506:5
#4 0x430a3e in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2ascii.c:90:17
#5 0x7f16f0c2f3d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

Direct leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x40f166 in __interceptor_malloc /opt/spack/c7.3/compilers-20181018/spack/var/spack/stage/llvm-6.0.1-bwifvlgg7krsnautcg5j4thwyvhz4gid/llvm-6.0.1.src/projects/compiler-rt/lib/lsan/lsan_interceptors.cc:54
#1 0x7f16f1b4195e in get_string /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/iodefs.h:482:18
#2 0x7f16f1b416f2 in dumpi_read_header /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:108:25
#3 0x7f16f1b42b4d in dumpi_open_input_file /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/common/io.c:506:5
#4 0x430a3e in main /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/dumpi2ascii.c:90:17
#5 0x7f16f0c2f3d4 in __libc_start_main (/lib64/libc.so.6+0x223d4)

SUMMARY: LeakSanitizer: 130 byte(s) leaked in 3 allocation(s).
Files callcounts-d2d-all-0001.bin.txt and /home/jpkenny/src/sst-macro-merge/sst-dumpi/dumpi/bin/../../tests/traces/callcounts-batch.txt differ

When reading a trace with libundumpi, the "thread" value passed to callbacks is always 0, regardless of the rank of the process that generated the trace in the first place. This is at least the case for traces available here: http://portal.nersc.gov/project/CAL/designforward.htm
(it can easily be checked by using dumpi2ascii, too).

Hi all, I'm playing with dumpi2otf and the example found at http://mpi.deino.net/mpi_functions/MPI_Intercomm_create.html, which crashes and issues the message "Error: trace::get_commentry: Invalid communicator index."

I'm wondering how to avoid this issue. Maybe this is a bug of libundumpi.

My analysis is the following:

1. "dumpi2otf -f dumpi-2017.11.22.12.28.10.meta -o TRACE.otf" returns the following lines (non-important lines are omitted):

MPI_Comm_split entering at walltime 79071.672523400, cputime 0.019312436 seconds in thread 0.
MPI_Comm oldcomm=2 (MPI_COMM_WORLD)
int color=0
int key=0
MPI_Comm newcomm=4 (user-defined-comm)
MPI_Comm_split returning at walltime 79071.672922008, cputime 0.019510788 seconds in thread 0.

MPI_Intercomm_create entering at walltime 79071.672924778, cputime 0.019513582 seconds in thread 0.
MPI_Comm localcomm=4 (user-defined-comm)
int localleader=0
MPI_Comm remotecomm=2 (MPI_COMM_WORLD)
int remoteleader=1
int tag=52
MPI_Comm newcomm=5 (user-defined-comm)
MPI_Intercomm_create returning at walltime 79071.766963076, cputime 0.064398238 seconds in thread 0.

MPI_Comm_free entering at walltime 79071.767282900, cputime 0.064599472 seconds in thread 0.
MPI_Comm comm=4 (user-defined-comm)
MPI_Comm_free returning at walltime 79071.767291600, cputime 0.064608163 seconds in thread 0.

MPI_Comm_free entering at walltime 79071.767293619, cputime 0.064610199 seconds in thread 0.
MPI_Comm comm=5 (user-defined-comm)
MPI_Comm_free returning at walltime 79071.767298083, cputime 0.064614646 seconds in thread 0.

MPI_Finalize entering at walltime 79071.767299452, cputime 0.064616031 seconds in thread 0.
MPI_Finalize returning at walltime 79071.771893553, cputime 0.066521156 seconds in thread 0.

2. After debugging, I think the problem is the function MPI_Comm_free that does not match the communicators created by MPI_Intercomm_create. dumpi2otf crashes in the function:

int trace::handle_comm_free(const dumpi_comm_free *prm, uint16_t thread,
            const dumpi_time *cpu, const dumpi_time *wall,
            const dumpi_perfinfo *perf, void *userarg) {
        (void) prm;
        (void) thread;
        (void) cpu;
        (void) wall, (void) perf;
        (void) userarg;
        trace *self = (trace*) userarg;
        std::cerr << "DEBUG:  trace::handle_comm_free comm=" << prm->comm << std::endl;
        commentry &the_comm = self->get_commentry(prm->comm); /* the_comm IS NOT FOUND */
        std::cerr << "DEBUG:  success" << std::endl;
        the_comm.freed = wall->stop;
        return 1;
}

trace::commentry& trace::get_commentry(int commhandle) {
        std::pair<commmap_t::iterator, commmap_t::iterator> it =
                this->comms_.equal_range(commhandle);
        if (it.first == it.second) // if no match was found.
            throw "trace::get_commentry:  Invalid communicator index."; /* OUR EXCEPTION */
        commmap_t::iterator ele = it.second;
        --ele;
        return ele->second;
}

3. If we run the command "dumpi2veft -i dumpi-2017.11.22.12.28.10.meta -o TRACE.otf" the output is:
   DEBUG: trace::handle_comm_free comm=4
   DEBUG: success
   DEBUG: trace::handle_comm_free comm=5
   Error: trace::get_commentry: Invalid communicator index.

4. I see that comm 4 is freed, whereas comm=5 is not.

Anyone know what may be happening. Any solution? suggestions?

Hi,

I am trying to install sst-dumpi on a Ubuntu 18.04.5 LTS system with a 5.7.9 kernel version.
I have downloaded the current master version (tagged with 7.1.0) and I have followed the configuration instructions, meaning that I've specified the --enable-libdumpi option and have specified CC and CXX parameters for make. Specifically, for CC / CXX I have tried mpicc and mpicxx from the 4.0, 1.8.1, and 1.10.7 OpenMPI codebases.

The configuration finishes fine, but I cannot build the system: the make fails in all versions of OpenMPI.

I get "conflicting types" errors for functions included both from the dumpi code as well as the OpenMPI code, and I've noticed that a type specification of dumpi is involved. Specifically: DUMPI_DEPRECATED_CONST.

I am attaching error logs with more information.

My issue is simlar to issues 5 and 7, that are already closed:
#5
#7

However, even when I apply the solutions proposed in there, I keep having the same problems.

Any hints on how I should proceed to have a successful installation?

Thanks!

error-4.0.log
error-1.10.7.log
error-1.8.1.log

DUMPI does not seem to be correctly remapping colors forDUMPI_UNDEFINED, leading to "real" communicator colors being undefined.

Hello,

I am using libdumpi to trace executions of the Graph500 BFS benchmark (specifically, the reference implementation available at: https://github.com/Graph500/graph500), and I have noticed that in records of MPI_Testany calls, there are some suspicious values for index and for the bytes field in the status. I have included below two examples that show both instances of the suspicious values.

Example 1:

MPI_Testany entering at walltime 56247.501448930, cputime 1.374186170 seconds in thread 0.
int count=4                                                                    
MPI_Request requests[4]=[6, 7, 8, 9]                                           
**int index=-32766**                                                               
int flag=0                                                                     
MPI_Status status=<IGNORED>                                                    
MPI_Testany returning at walltime 56247.501454870, cputime 1.374192287 seconds in thread 0.

Example 2:

MPI_Testany entering at walltime 56247.502554376, cputime 1.375274547 seconds in thread 0.
int count=4                                                                    
MPI_Request requests[4]=[10, 11, 12, 13]                                       
int index=0                                                                    
int flag=1                                                                     
MPI_Status status=[{**bytes=-32766**, cancelled=0, source=0, tag=2048, error=0}]   
MPI_Testany returning at walltime 56247.502558329, cputime 1.375278986 seconds in thread 0.

Since the suspicious value in both cases is -32766, I suspect an overflow issue, but I am not sufficiently familiar with MPI, libdumpi, and the benchmark I'm tracing to completely rule out other causes. Can someone confirm whether this is actually a bug? Thanks.

Hi all,

I was trying to configure using

../configure CC=mpicc CXX=mpicxx --enable-libdumpi --prefix=/home/jon/Opt/dumpi

and then i got the error that:

checking whether mpi.h is found... configure: error: in /home/jon/sst-dumpi/build': configure: error: no See config.log' for more details

I cannot seem to find hints from config.log

Can anyone help me with the issue? I installed mpi on ubuntu16.04.

Thanks,

Hi,
When I use DUMPI for collecting trace in NAS Benchmarks, no DUMPI binary files generated. i.e. at IS benchmark, I modified the makefile by adding dumpi to CMPI_LIB :

It can compile and execute the libdumpi_enable_profiling() call in the is.c without any error, but no DUMPI binary files generated.

I am trying to build sst-dumpi from source with the following configuration line:
../configure --enable-libdumpi --enable-libundumpi --prefix=/home/harsh/sst-dumpi/install CC=mpicc CXX=mpicxx

This is on a ubuntu system. I have also tried this on a OS X machine. I get the following error when I make:
../../../dumpi/libdumpi/mpibindings2.c: At top level:
../../../dumpi/libdumpi/mpibindings2.c:187:5: error: conflicting types for ‘MPI_Send’
int MPI_Send(DUMPI_CONST void *buf, int count, MPI_Datatype datatype, int dest,
^
In file included from ../../../dumpi/libdumpi/data.h:48:0,
from ../../../dumpi/libdumpi/mpibindings-maps.h:50,
from ../../../dumpi/libdumpi/mpibindings.h:48,
from ../../../dumpi/libdumpi/mpibindings2.c:46:
/usr/lib/openmpi/include/mpi.h:1679:20: note: previous declaration of ‘MPI_Send’ was here
OMPI_DECLSPEC int MPI_Send(const void *buf, int count, MPI_Datatype datatype,
^
../../../dumpi/libdumpi/mpibindings2.c:255:5: error: conflicting types for ‘MPI_Get_count’
int MPI_Get_count(DUMPI_CONST MPI_Status *status, MPI_Datatype datatype, int *c
^
In file included from ../../../dumpi/libdumpi/data.h:48:0,
from ../../../dumpi/libdumpi/mpibindings-maps.h:50,
from ../../../dumpi/libdumpi/mpibindings.h:48,
from ../../../dumpi/libdumpi/mpibindings2.c:46:
/usr/lib/openmpi/include/mpi.h:1455:20: note: previous declaration of ‘MPI_Get_count’ was here
OMPI_DECLSPEC int MPI_Get_count(const MPI_Status *status, MPI_Datatype datatyp
^
../../../dumpi/libdumpi/mpibindings2.c:287:5: error: conflicting types for ‘MPI_Bsend’
int MPI_Bsend(DUMPI_CONST void *buf, int count, MPI_Datatype datatype, int dest
^
In file included from ../../../dumpi/libdumpi/data.h:48:0,
from ../../../dumpi/libdumpi/mpibindings-maps.h:50,
from ../../../dumpi/libdumpi/mpibindings.h:48,
from ../../../dumpi/libdumpi/mpibindings2.c:46:
/usr/lib/openmpi/include/mpi.h:1235:20: note: previous declaration of ‘MPI_Bsend’ was here

And so on...

Hi,
I am using the dumpi library with instrumentation using libdumpi_enable_profiling and call libdumpi_disable_profiling()routines in a FORTRAN77 code.

I build the code with "-I/projects/Performance/chunduri/sst-dumpi/install/include -L/projects/Performance/chunduri/sst-dumpi/install/lib -ldumpif77 -ldumpi".

The build process completed without any issues, however, when running the code, it generates the following error:

Rank 1378 [Thu Jul 20 02:48:45 2017] [c1-1c2s10n2] Fatal error in MPI_Attr_get: Invalid argument, error stack:
MPI_Attr_get(141): MPI_Attr_get(MPI_COMM_WORLD, keyval=1681915906, attr_value=0x7fffffff63e4, flag=0x7fffffff6290) failed
MPI_Attr_get(99).: The attribute value is not the address of a pointer or pointer-sized integer. A common error is to pass the address of an integer to any of the MPI_Xxx_get_attr routines on systems where the size of a pointer is larger than the size of an integer.
.....
....
Similar error reported from each MPI rank. I suspect this to be a FORTRAN - C interoperability issue.

Can you suggest anyways to resolve this.

Thanks
Sudheer

I am using pytorch to train model.I want to get trace file using dumpi.But I don't know how to deal with.Can you help me ?

Hi,

I am trying to install dumpi library when I encountered the problem. When I cloned the git and was tryign to run ./bootstrap.sh, the terminal prompted an error saying

./bootstrap.sh: 14: ./bootstrap.sh: glibtoolize: not found
./bootstrap.sh: 15: ./bootstrap.sh: autoreconf: not found

I am wondering how did it happen and how to solve it.

Thanks,