Hi Brian, Thanks for reporting this. It certainly looks like a bug in DMTCP. I am able to reproduce the same behavior locally. In my case, I used the DMTCP master with stress ver. 1.0.4. I will let you know when I make more progress on this. I'll also file it as a bug on Github (https://github.com/dmtcp/dmtcp/issues), it'll be easier to track this issue.
-Rohan ----- Original Message ----- From: "Brian Koebbe" <koe...@wustl.edu> To: "dmtcp-forum" <dmtcp-forum@lists.sourceforge.net> Sent: Wednesday, June 3, 2015 12:03:24 PM Subject: [Dmtcp-forum] simple test using "stress" never completes after one checkpoint/restart Hi all, I'm not a complete newbie... but I've got a super simple DMTCP test that I can't seem to get working. OS: Ubuntu 14.10 (kernel 3.16.0) DMTCP versions: 2.3.1, and github master (as of this morning) (./configure;make;make install) $ apt-get install stress Terminal 1: $ dmtcp_launch stress --vm 2 --vm-bytes 128M --timeout 30s Terminal 2 (after 10 seconds): $ dmtcp_command -cb $ dmtcp_command -k Terminal 1: $ ./dmtcp_restart_script.sh ** Never finishes, just "spins" with a couple DMTCP:stress processes ** I can certainly send more debug info, but first I just want to make sure I'm not overlooking something. Any help would be greatly appreciated, Brian ------------------------------------------------------------------------------ _______________________________________________ Dmtcp-forum mailing list Dmtcp-forum@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dmtcp-forum ------------------------------------------------------------------------------ _______________________________________________ Dmtcp-forum mailing list Dmtcp-forum@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dmtcp-forum