some of the _magicBits in DmtcpMessage-constructor, "dmtcpmessagetypes.cpp", are not initialized. This is not a bug,
but to get rid of a valgrind uninitialized warning when running something like
valgrind dmtcp_checkpoint ./dmtcpcheckpointtest
you have to initialize all bits first, for example with memset(_magicBits , '\0', 16);
strncpy ( _magicBits,DMTCP_MAGIC_STRING,sizeof ( _magicBits ) );
If I also run the under dmtcp_coordinator in another terminal first, I always get uninitialized warning when calling
valgrind dmtcp_checkpoint ./dmtcpcheckpointtest,
but I did not identified the cause until yet.