Try running as sage -gdb , which will catch the error. Then you can type "bt" at the prompt to get a c traceback.
On Sep 15, 2008, at 2:41 PM, Simon King wrote: > > Dear team, > > in some Cython module, i am raising an error, as i often did without a > problem. But this time, raising the error resulted in a crash: > /home/king/SAGE/devel/sage-3.1.1/local/bin/sage-sage: line 216: 23605 > Speicherzugriffsfehler sage-ipython "$@" -c "$SAGE_STARTUP_COMMAND;" > > Does anyone have an idea what can be the reason? Or at least where i > may start digging? > > I am really puzzled, so much that i even have no idea what additional > information might help to trac the error. Just as a test, i inserted a > print command right before raising the error. The print command > worked, but then Sage quit without even saying good bye. > > Yours > Simon > > > --~--~---------~--~----~------------~-------~--~----~ 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 URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
