This web page shows the issues in the functions in the package lineup2 if there are any. The table below shows the list of inputs passed that are generated by fuzzers and the valgrind issues with corresponding CPP file and line number.
| name | inputs | message | file.line | valgrind_log | executable.file |
|---|---|---|---|---|---|
| lineup2:::corr_betw_matrices_paired | x y | 41 bytes in 1 blocks are possibly lost in loss record 21 of 1,321 | corr_betw_matrices.cpp : 16 | valgrind_log | executable-test-file |
| lineup2:::corr_betw_matrices_unpaired_all | x y | 43 bytes in 1 blocks are possibly lost in loss record 21 of 1,322 | corr_betw_matrices.cpp : 169 | valgrind_log | executable-test-file |
| lineup2:::corr_betw_matrices_unpaired_bestpairs | corr_threshold x y | 43 bytes in 1 blocks are possibly lost in loss record 21 of 1,324 | corr_betw_matrices.cpp : 118 | valgrind_log | executable-test-file |
| lineup2:::corr_betw_matrices_unpaired_bestright | x y | 43 bytes in 1 blocks are possibly lost in loss record 21 of 1,322 | corr_betw_matrices.cpp : 52 | valgrind_log | executable-test-file |
| lineup2:::fscale | x y | 47 bytes in 1 blocks are possibly lost in loss record 23 of 1,322 | fscale.cpp : 15 | valgrind_log | executable-test-file |
| lineup2:::mad_betw_matrices | x y | 43 bytes in 1 blocks are possibly lost in loss record 21 of 1,322 | dist_betw_matrices.cpp : 51 | valgrind_log | executable-test-file |
| lineup2:::propdiff_betw_matrices | x y | 43 bytes in 1 blocks are possibly lost in loss record 21 of 1,323 | dist_betw_matrices.cpp : 87 | valgrind_log | executable-test-file |
| lineup2:::rmsd_betw_matrices | x y | 43 bytes in 1 blocks are possibly lost in loss record 21 of 1,322 | dist_betw_matrices.cpp : 17 | valgrind_log | executable-test-file |