sage -gdb will start Sage with the ability to fall to gdb when interrupted with ctrl-c. If you have your C file handy produced from Cython you can set breakpoints there and so on. As said it's easy to see which Cython command is represented by the C code.
On Tue, May 3, 2016, 19:30 john_perry_usm <[email protected]> wrote: > On Monday, May 2, 2016 at 1:56:55 PM UTC-5, Ralf Stephan wrote: >> >> That you can't trace Cython is fortunately not true. >> I do it from time to time using gdb when I trace pynac code. >> > > Can you trace Cython *in Sage*? If so, I was genuinely unaware of that > (or forgot). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "sage-support" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/sage-support/0PEjhQQ1AAE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
