Menu

#3 Silence valgrind memcheck error by memset()-ing pkt to 0

current
open
None
5
2014-08-19
2014-05-10
No

valgrind reports:

Syscall param write(buf) points to uninitialised byte(s)

In this case, it is a false positive, but adding this single memset at
attach start-up means the program is now clean when run with "valgrind
--trace-children=yes dtach -c ...", which can make future debugging
easier.

1 Attachments

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.