I've got the segfault on amd64 (Intel Core2). I ran with sage -gdb, once the segfault hits, a bt gives:
(gdb) bt #0 0x00007f4808262050 in strlen () from /lib/libc.so.6 #1 0x0000000000455e4b in PyString_FromString () #2 0x00007f47effbda43 in initmulti_polynomial_libsingular () from /usr/lib/python2.5/site-packages/sage/rings/polynomial/multi_polynomial_libsingular.so #3 0x00000000004ab1d7 in _PyImport_LoadDynamicModule () #4 0x00000000004a9734 in ?? () #5 0x00000000004a99cc in ?? () #6 0x00000000004aa071 in ?? () #7 0x00000000004aa3df in PyImport_ImportModuleLevel () #8 0x000000000048ad79 in ?? () #9 0x00000000004187b3 in PyObject_Call () #10 0x000000000048b262 in PyEval_CallObjectWithKeywords () #11 0x000000000048e822 in PyEval_EvalFrameEx () #12 0x0000000000492a52 in PyEval_EvalFrameEx () #13 0x000000000049313d in PyEval_EvalCodeEx () #14 0x00000000004dd612 in ?? () #15 0x00000000004187b3 in PyObject_Call () #16 0x00007f47fe4101c8 in ?? () from /usr/lib/python2.5/site-packages/sage/rings/ring.so #17 0x00000000004187b3 in PyObject_Call () #18 0x0000000000462194 in ?? () #19 0x000000000048f03c in PyEval_EvalFrameEx () Incidentally, sage -notebook does not give a segfault. It doesn't really help though. I presume you need to type shift-enter to get a result in the notebook? It's not documented! But that's how you do it in Mathematica. Anyway, even after pressing shift-enter, it doesn't give any output result. Probably silently affected by the segfault. Drew -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
