#4 dmtcp_checkpoint_filename uninitialized in mtcp.c

closed-fixed
nobody
None
2010-07-20
2010-07-19
Anonymous
No

Uninitialized 'dmtcp_checkpoint_filename' leads to a SEGFAULT in mtcp.c (line 1495) ,
DMTCP Version: 1.1.8

solution : initialize 'dmtcp_checkpoint_filename' to NULL no later than line 1466
(mtcp.c: line 1467: "if (callback_pre_ckpt != NULL)")

Discussion

  • Gene Cooperman

    Gene Cooperman - 2010-07-19

    Thanks very much for the bug fix. I have added your bug fix to the svn,. It will be included in the next release, and anyone using the svn will benefit from your fix immediately. I am guessing that this bug only affected users who were using MTCP standalone (without DMTCP). Is that correct? (Otherwise, callback_pre_ckpt will be non-NULL and dmtcp_checkpoint_filename will be initialized.) If so, I am curious about your application that uses MTCP standalone.

    (If you prefer not to login to sourceforge, you can always write to my direct e-mail address: gene@ccs.neu.edu )
    Best wishes, - Gene

     
  • Nobody/Anonymous

    >Thanks very much for the bug fix
    My pleasure!

    >I am guessing that this bug onlyaffected users who were using MTCP standalone
    Yes, I used MTCP standalone (MTCP sufficed my current needs), but I will try out DMTCP also.

    Cheers,
    Jack

     
  • Gene Cooperman

    Gene Cooperman - 2010-07-20
    • status: open --> closed-fixed
     

Log in to post a comment.