Files
iverilog/ivtest/find_valg_all
T
Stephen Williams cea237b407 Add ivtest to the iverilog source tree
By adding ivtest to the iverilog source tree, it is easier to keep
the regression test synchronized with the source that is being tested.
This should be especially helpful for PRs that add a new feature, and
have a matching ivtest PR with the regression test for that feature.
2022-01-15 10:18:50 -08:00

38 lines
1.4 KiB
Bash
Executable File

#!/bin/sh
echo "VVP valgrind errors."
echo "-------------------------"
fgrep "ERROR SUMMARY" log/*.log | fgrep -v " 0 errors" || echo "No Errors."
tail -n8 log/*.log | fgrep "definitely lost" | fgrep -v " 0 bytes" || \
echo "No \"definitely lost\" memory in vvp."
tail -n8 log/*.log | fgrep "indirectly lost" | fgrep -v " 0 bytes" || \
echo "No \"indirectly lost\" memory in vvp."
tail -n8 log/*.log | fgrep "possibly lost" | fgrep -v " 0 bytes" || \
echo "No \"possibly lost\" memory in vvp."
tail -n8 log/*.log | fgrep "still reachable" | fgrep -v " 0 bytes" || \
echo "No \"still reachable\" memory in vvp."
# egrep "^\*\*[0-9]+\*\*" log/*.log || echo "No \"missed deletes\" in vvp."
echo ""
echo "VPI valgrind errors."
echo "-------------------------"
fgrep "ERROR SUMMARY" vpi_log/*.log | fgrep -v " 0 errors" || echo "No Errors."
tail -n8 vpi_log/*.log | fgrep "definitely lost" | fgrep -v " 0 bytes" || \
echo "No \"definitely lost\" memory in vvp."
tail -n8 vpi_log/*.log | fgrep "indirectly lost" | fgrep -v " 0 bytes" || \
echo "No \"indirectly lost\" memory in vvp."
tail -n8 vpi_log/*.log | fgrep "possibly lost" | fgrep -v " 0 bytes" || \
echo "No \"possibly lost\" memory in vvp."
tail -n8 vpi_log/*.log | fgrep "still reachable" | fgrep -v " 0 bytes" || \
echo "No \"still reachable\" memory in vvp."
# egrep "^\*\*[0-9]+\*\*" vpi_log/*.log || echo "No \"missed deletes\" in vvp."