On Wed, May 4, 2011 at 3:05 PM, Robert Bradshaw <rober...@math.washington.edu> wrote: > On Wed, May 4, 2011 at 2:16 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: >> On 2011-05-04 23:06, Robert Bradshaw wrote: >>> Are you returning a non-python object in a cdef method without an >>> "except" signature? >> This is not the issue. >> >> I think that *somewhere* in Sage a KeyboardInterrupt exception is caught >> by an "except:" (i.e. except everything) and I want to know where. > > You could try using pdb. Other than that, I'm not sure.
Oh, if you're really desperate, you could put in a gdb breakpoint and step forward from there. >> One >> example is #7702 and while merging sage-4.7.1.alpha0 I discovered >> another instance: KeyboardInterrupt raised by the sig_on() in >> sage/matrix/matrix_integer_dense.pyx in _zero_out_matrix() while >> executing J1(12345).hecke_operator(997). >> >>> Turning on profiling is another way to get call stacks. >> Do you have any pointers for this? > > http://docs.cython.org/src/tutorial/profiling_tutorial.html > >> 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 >> > -- 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
