When dmtcp_launch is called in a shell, on restart the process is in background (even if interactive)

[gc00]

Place dmtcp_launch -i40 R (or python -i) inside a shell script, and then run the shell script. And then run a Python program, in my case. Then on restart, the interactive process is in background, and one cannot interact with it.

@JainTwinkle, I'm documenting the bug here. I should be able to get to implementing the fix soon.

To reproduce, create tmp.sh:

#!/bin/sh
dmtcp_launch -i 40 python -i

Then execute tmp.sh, and interactively do:

import time
for i in range(1000):
  print(i)
  time.sleep(1)

Then, after it checkpoints, kill it, and restart as: dmtcp_restart ckpt_python*.dmtcp
On restart, I explicitly see:

[40000] WARNING at terminal.cpp:92 in restore_term_settings; REASON='JWARNING(false) failed'
Message: :skip restore terminal step -- we are in BACKGROUND

The warning is courteous enough to tell us to look at 'terminal.cpp', line 92.

See PR #904 for a description of the bug, and a fix for this bug.