In fact, it really appears as though the place the code is getting stuck at *is* properly wrapped with _sig_on and _sig_off. What could be happening?
On Wed, Mar 17, 2010 at 3:50 PM, Robert Miller <r...@rlmiller.org> wrote: > I'm having a frustrating time with this... > > I'm using signal.alarm to time out computations that take too long. In > most cases they work, but sometimes they don't. The CPU stops > spinning, but I don't get my prompt back, the program just hangs > forever. I know this is due to a lack of sig_on/sig_off clauses > somewhere, but I don't know where they belong. This is the kind of > thing where I could run it over and over and have the interruption > work, but one in a hundred times it doesn't work. In that one out of a > hundred times, is there any possible way to know where the problem is > occurring? > > -- > Robert L. Miller > http://www.rlmiller.org/ > -- Robert L. Miller http://www.rlmiller.org/ -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
