Pardon the newbie question, Is there a quick way to get backtraces for doctest failures?
I have been running gdb python in a sage subshell, then copying the offending lines into a text file and then running from within gdb. This seems to be awkward and I was looking for a better way. This is my first foray into serious debugging so I do not have a good workflow. -- David Monarres dmmonar...@gmail.com "There... I've run rings 'round you logically" -- Monty Python's Flying Circus On Nov 13, 2009, at 3:44 PM, William Stein wrote: > > On Fri, Nov 13, 2009 at 3:42 PM, David M. Monarres <dmmonar...@gmail.com> > wrote: >> >> Thanks for the information, that is why I had asked. I have never really dug >> this deep into sage before, (nor software building in general) so I am >> completely green. >> >> Saw this posting on macports + the output of otool -L made me think that >> this could be the problem. But I agree that it isn't likely. >> > > Probably not. That said, in debugging (and problem solving in > general), it's generally a good idea to be very skeptical of anything > a person who has failed to solve a problem (in this case, me) tells > you. > > William > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
