On Thu, May 28, 2009 at 8:47 AM, ksk...@gmail.com <ksk...@gmail.com> wrote: > > I've built several recent versions of Sage on the same box (a 64-bit > Opteron running Fedora 10), and it seems pretty consistently that > attempting to use a tab completion causes a segmentation fault. For > instance:
I can replicate this problem on my Fedora 10 64-bit Sage install even with sage-4.0.rc1. This is now trac #6151: http://trac.sagemath.org/sage_trac/ticket/6151 -- William > > ---------------------------------------------------------------------- > | Sage Version 3.4.1, Release Date: 2009-04-21 | > | Type notebook() for the GUI, and license() for information. | > ---------------------------------------------------------------------- > sage: P.<x> = PolynomialRing(QQ) > sage: P. > > ------------------------------------------------------------ > 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). > ------------------------------------------------------------ > > /scratch/sage-x64/local/bin/sage-sage: line 198: 30653 Segmentation > fault sage-ipython "$@" -i > > I think mabshoff suggested at one point that this may be due to my > stack size being too small...? > > Kiran > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
