This web page shows the issues in the functions in the package segclust2d 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 |
|---|---|---|---|---|---|
| segclust2d::DynProg_algo_cpp | Kmax matD | 100 bytes in 1 blocks are possibly lost in loss record 44 of 1,323 | SegTraj_DynProg.cpp : 20 | valgrind_log | executable-test-file |
| segclust2d:::apply_rowSums | rupt x | 61 bytes in 1 blocks are possibly lost in loss record 28 of 1,291 | SegTraj_EM.cpp : 59 | valgrind_log | executable-test-file |
| segclust2d:::arma_repmat | |||||
| segclust2d:::colsums_sapply | i mu rupt tau x | 74 bytes in 1 blocks are definitely lost in loss record 35 of 1,326 | SegTraj_EM.cpp : 99 | valgrind_log | executable-test-file |
| segclust2d:::cumsum_cpp |