On Fri, Apr 24, 2015 at 1:12 AM, Gene Cooperman <g...@ccs.neu.edu> wrote:
> Thanks for reporting this bug. Thanks for quick reply. I am not sure what is a bug? As far as 2.4 goes I am probably doing something wrong so that probably isn't a bug. I sent this before, but I did not send to the list, and my email address was wrong so I would not see replies you sent. Sorry for the second near-identical copy (last paragraph has new info) > To be honest, when DMTCP was growing > fast, we weren't paying enough attention to issues such as ctrl-C. It sounds like you are saying that you know already know this behavior exists in 2.2 and 2.3? Or should I be able to build those and have them work as one would want with control-c? If this is already known to be an issue that is a bit of a relief since at least I know what it is and it was then fixed in 2.4. > If 2.4.0 rc2 sometimes segfaults on restart, we'd definitely like to > reproduce that locally here, and fix it. > Here are some questions that will help us to analyze this: > 1. Which programming language interpreter were you testing on? I tried python, R, and ocaml. > 2. On the netbook, was the Atom a 32-bit CPU or 64-bit? It is an Atom N550, that is 64bit, but it is running under a 32 bit Fedora with all code in 32 bit. I assumed a vanilla configure would detect this, which it seems to have, otherwise it would not have run at all. But I see now in the install there is an --enable-m32 option discussed. I assume this is just for mixed 32/64 bit use, but I tried building that one, and had the same result, and also without the default first make. (I assume all three of these in this situation actually did the same thing). Stracing the run always has it stop in the same place, after a call to set_thread_area. I can try to run some gdb's or such if you say what you could use. > 3. You said that on the Fedora 20 machine with 2.4.0 rc2, the > restart would _sometimes_ segfault. Given a single checkpoint image, > would that same image sometimes checkpoint on restart? Or would > the same file always segfault on restart, and a new checkpoint image > might always restart? (In other words, is there sometimes a > "bad ckpt image" that will always segfault on restart, or is it > that a single ckpt image will sometimes segfault on restart and > sometimes not?) It is all with a single image. Each single image starts most of the time, and occasionally does not. I would not put much stock in this, since I might have some kind of RAM problem. I had two random crashes a few weeks ago, and although long memtest86 runs detected nothing, who knows? Nothing else is causing any symptoms at current. Also (added in second message) I have since built 2.3.1 on the 64 bit i3 540 Fedora 20, and it works all the time with no segfaults on anything I throw at it, but it still has the problem from 2.2, and the problem of the 32 bit 2.3 on the Atom processor: that is, a control-c kills the process outright instead of letting the interpreter handle the interrupt. ------------------------------------------------------------------------------ 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 Dmtcp-forum@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
