Memory Leak Testing#34
Merged
Merged
Conversation
Leak caused by copying more bytes than res holds
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Memory Leak Testing
Add memory leak testing with the
AddressSanitizeravailable inclang. Closes #16.Tests
make leaksruns leak tests based on different command line argsmake testchecks the separate functions in disco for leaksmake leakstests/leaks.shto print sanitizer output in a user-friendly way when running multiple tests:Fix Memory Leaks
The tests revealed multiple leaks which are now fixed:
pcap_compile()filters where not freed insrc/arp.corsrc/syn_scan.cif_namevariable was not freed insrc/arp.csrc/utils.ccaused copying of bytes outside of allocated memoryifwas used instead ofelse ifinsrc/ping.cwhich caused a use-after-free of thedstvariableREADME
Update README