This web page shows the issues in the functions in the package lpirfs 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 |
|---|---|---|---|---|---|
| lpirfs:::hp_filter | lambda x | 136 bytes in 1 blocks are possibly lost in loss record 51 of 1,320 | hp_filter.cpp : 56 | valgrind_log | executable-test-file |
| lpirfs:::newey_west | h x y | 68 bytes in 1 blocks are definitely lost in loss record 34 of 1,326 | newey_west.cpp : 37 | valgrind_log | executable-test-file |
| lpirfs:::newey_west_pw | D_mat h hhat_mat xpxi_mat | 67 bytes in 1 blocks are definitely lost in loss record 34 of 1,327 | newey_west_pw.cpp : 76 | valgrind_log | executable-test-file |
| lpirfs:::newey_west_tsls | h x y z | 92 bytes in 1 blocks are possibly lost in loss record 45 of 1,325 | newey_west_tsls.cpp : 38 | valgrind_log | executable-test-file |
| lpirfs:::ols_diagnost | x y | 68 bytes in 1 blocks are definitely lost in loss record 34 of 1,323 | ols_diagnost.cpp : 60 | valgrind_log | executable-test-file |
| lpirfs:::var_one | VAR_Data | 79 bytes in 1 blocks are possibly lost in loss record 37 of 1,323 | var_one.cpp : 36 | valgrind_log | executable-test-file |