Rohan

Thank you for reporting this issue, @rdp-dn. I can reproduce this issue locally. I'll try to see if I can come up with a fix.

The issue here is a deadlock, illustrated by the stack trace below. ``` Thread 3 (Thread 0x7f2bb96f5700 (LWP 973)): #0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x00007f2bc3550e42 in __GI___pthread_mutex_lock (mutex=0x3000226948 )...

Thanks for the fix @JainTwinkle. I have a general design question before I start looking at the patch. Why can't we change `dmtcp_getttid()` to make the gettid syscall (`_real_syscall(SYS_gettid)`), do...

@karya0: Would you have time to look at this?

Sorry about the slow progress on this, @koebbe. We have been a bit busy with various deadlines, but haven't forgotten about the pending issues. :-) So, I started investigating this...

The issue reported in PR #743 is another example of this issue. I think the patch there fixes this partially, but not completely.

@karya0: It works for simple programs; it fails for programs that call fork, for example, the client-server test, forkexec test, etc.

@gc00: I have noticed that screen and posix-mq2 are failing on dekaksi, but I haven't had time to investigate the root cause. > After that, even the first posix-mq1 fails....

@MikeDacre It's difficult to have a one-size-fits-all solution for files. The good thing is that there are various runtime options, callbacks and plugins that can help you customize the behavior....

@MikeDacre Please find my answers below. > What I would love to be able to do is to submit jobs with a DMTCP wrapper, and then monitor them as they...