#7 some of the _magicBits in DmtcpMessage-object uninitialized

open
None
2010-09-09
2010-08-02
No

Hello,

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);
before calling
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.

Jack

Discussion

  • Jakob Kroeker

    Jakob Kroeker - 2010-08-02

    valgrind also detects some minor memory leaks

     
  • Jakob Kroeker

    Jakob Kroeker - 2010-08-02
    • priority: 5 --> 3
     
  • Kapil Arya

    Kapil Arya - 2010-09-09
    • assigned_to: nobody --> karya
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks