Hi Calvin,
I have now confirmed the problem with ocaml on the local 64-bit
computer of our team (currently Ubuntu 13.10). No doubt, the same bug
would appear on the other computers that we test on. This is good news.
If we can observe it locally, we should have a good chance of fixing it.
From what I can tell so far, ocaml really tries to defend itself
against the user typing ^C (and maybe from the user sending other signals).
DMTCP tries to support such behavior in a non-invasive way while still
working correctly. Clearly DMTCP is failing to do so in the case of ocaml.
Thanks again for reporting this. (And as I remarked early, we'll
also look at the support for 32-bit O/S's, once we put out rc4.
rc2 and rc3 are known to have problems with a 32-bit O/S.)
Best,
- Gene
------------------------------------------------------------------------------
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
