On Sat, Jun 5, 2010 at 9:41 PM, François Bissey <f.r.bis...@massey.ac.nz> wrote: > ./sage > ---------------------------------------------------------------------- > | Sage Version 4.4.3, Release Date: 2010-06-04 | > | Type notebook() for the GUI, and license() for information. | > ---------------------------------------------------------------------- > > > ------------------------------------------------------------ > Unhandled SIGSEGV: A segmentation fault occured in Sage. > This probably occured because a *compiled* component > of Sage has a bug in it (typically accessing invalid memory) > or is not properly wrapped with _sig_on, _sig_off. > You might want to run Sage under gdb with 'sage -gdb' to debug this. > Sage will now terminate (sorry). > ------------------------------------------------------------ > > OOPS. so this was originally a sage 4.4.1 upgraded to 4.4.2 > and this afternoon to 4.4.3. > > I have a backtrace that stops at ginac: > #0 0x00000000 in ?? () > #1 0xb262609f in GiNaC::Number_T::is_integer (this=0x90ed8b4) at > numeric.cpp:945 > #2 0xb2626150 in GiNaC::numeric::is_integer (this=0x90ed8a0) at > numeric.cpp:1945 > #3 0xb26337f1 in GiNaC::power::eval (this=0xbfc91bc0, level=1) at > power.cpp:634 > #4 0xb254cffa in GiNaC::ex::construct_from_basic (oth...@0xbfc91bc0) at > ex.cpp:312 > #5 0xb262d417 in GiNaC::operator/ (l...@0xbfc91cc8, r...@0xbfc91cbc) at > ex.h:266 > #6 0xb25ab752 in exp_eval (x...@0x9b92430) at inifcns_trans.cpp:88 > #7 0xb256d6e3 in GiNaC::function::eval (this=0xbfc91eac, level=1) at > function.cpp:1412 > #8 0xb254cffa in GiNaC::ex::construct_from_basic (oth...@0xbfc91eac) at > ex.cpp:312 > #9 0xb243e088 in __pyx_pf_4sage_8symbolic_10expression_10Expression_exp > (__pyx_v_self=0x9b63f6c, unused=0x0) > at > /home/francois/Work/sandbox/install/sage-4.4.1/local//include/pynac/ex.h:266 > #10 0xb75fc831 in PyCFunction_Call (func=0x9b482ac, arg=0xb736f02c, kw=0x0) at > Objects/methodobject.c:90 > #11 0xb75ba7ec in PyObject_Call (func=0x9b482ac, arg=0xb736f02c, kw=0x0) at > Objects/abstract.c:2492 > #12 0xb2321a02 in __pyx_pf_4sage_8symbolic_11constants_c_1E___init__ > (__pyx_v_self=0x9b63f4c, __pyx_args=0xb736f02c, > __pyx_kwds=0x0) at sage/symbolic/constants_c.cpp:1960 > > > Anything else I should look for? I am personally suspecting the python upgrade > not to be very smooth. > > Francois
It couldn't hurt to force a rebuild of pynac (or failing that Python). sage -f pynac-0.2.0.p3 Fortunately, whatever happened isn't going to happen to *everybody*. I tested upgrading from 4.4.2 to 4.4.3 on our development server, and it worked fine. William -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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
