On Thu, Apr 23, 2015 at 8:52 PM I wrote: > I want to checkpoint a programming language interpreter's environment > which I am using interactively. When using this environment, if an > expression I am evaluating turns out not to help, normally I can hit > control-c to interrupt the computation and return me to the > enviroment's user prompt.
Oops, that should be "turns out not to *halt*". Some more details. I was using the dmtcp that comes with Fedora 20, which was version 2.2. So I tried the newest version 2.4.0 rc2, and it does pass the control-c as expected to the process that was checkpointed. However, I find that 2.4.0 rc2 occasionally segfaults when starting up a restart. Next I tried on my netbook (which is an Atom processor, the other machine is an i3 540). I first tried the 2.4.0 rc2 version with a default ./configure. It checkpoints the process without complaint, but without fail segfaults on the restart. So I tried 2.3.1, and it has the same problem as the 2.2 on the other machine does: it quits completely when it gets a control-c. Is it correct to assume that control-c never did work correctly in earlier versions and that is one thing that is being fixed in 2.4? I might assume this since I have two separate examples where the control-c had this behavior in pre 2.4 versions. But this seems unlikely since the control-c behavior is so standard and so needed by so many. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Dmtcp-forum mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
