On 2/1/12 1:15 PM, Starx wrote:
Ok, I've found a minimal example that crashes sage and doesn't involve
my code so it should be easier to debug. The following crashes sage:
sage: X = (GF(3)^1)/(GF(3)^0)
sage: Y = (GF(3)^1)/(GF(3)^1)
sage: X.hom([(1,)], Y)
But since it crashes all the way out to the prompt I can't use sage's
debugger to look into it any further. When I type import pdb;
pdb.set_trace() it goes straight into a debugger before I get a chance
to actually crash anything. How can I get a debugger to run so that I
can maybe find an error?
I'd put "import pdb; pdb.set_trace()" inside the code the X.hom() method
(don't forget to do "sage -br" to incorporate that change into the
running Sage). That will start the debugger there, and then you can
step through things.
You could also put print statements in the appropriate places in the
code, do "sage -br" to compile the print statements, and run again. It
seems that the problem is happening somewhere in the modn_dense_float
class for vectors, possibly in a call to LinBox. My guess is that it is
either a LinBox bug, or we are calling the LinBox function with bad input.
Thanks,
Jason
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
