sage-5.7.beta2 released

[Jeroen Demeyer]

Dear Sage lovers,

We're releasing Sage 5.7.beta2.

Source archive:

http://boxen.math.washington.edu/home/release/sage-5.7.beta2/sage-5.7.beta2.tar

Upgrade path:

http://boxen.math.washington.edu/home/release/sage-5.7.beta2/sage-5.7.beta2/

The source and upgrade path can also be found on the mirror network
(you might need to wait a while before the mirrors are synchronized):

http://www.sagemath.org/download-latest.html


Please build, test, and report! We'd love to hear about your
experiences with this release.

== Tickets ==

* We closed 94 tickets in this release. For details, see

http://boxen.math.washington.edu/home/release/sage-5.7.beta2/tickets.html

Closed tickets:

#13950: Robert Bradshaw: Sage-patchbot improvements [Reviewed by Volker
Braun]

Merged in sage-5.7.beta2:

#5562: Christian Nassau: coercion error with vectors and polynomial
rings with 1 variable [Reviewed by Travis Scrimshaw]
#9921: John Palmieri: nose testing suite as an optional spkg [Reviewed
by Karl-Dieter Crisman, Martin Raum]
#11672: Marc Mezzarobba: Some more doctests from the book "Calcul
mathématique avec Sage" [Reviewed by Martin Albrecht, Charles Bouillaguet]
#12014: Radoslav Kirov, Punarbasu Purkayastha: Make linearcode.__iter__
and linearcode.list() faster [Reviewed by Dmitrii Pasechnik]
#13077: Frédéric Chapoton: generalised Tamari lattices [Reviewed by
Christian Stump, Hugh Thomas]
#13204: Travis Scrimshaw: Element construction for CrystalOfTableaux
should be robust versus int's [Reviewed by Anne Schilling]
#13667: Dmitrii Pasechnik, Punarbasu Purkayastha: fix docs in
sage/coding/code_bounds.py [Reviewed by Punarbasu Purkayastha, Dmitrii
Pasechnik]
#13687: Volker Braun: Parents for groups [Reviewed by David Roe]
#13763: Volker Braun: Minkowski subtraction [Reviewed by Dmitrii Pasechnik]
#13765: Robert Bradshaw: Cyclotomic embeddings should respect coercions.
[Reviewed by Frédéric Chapoton, Stephan Ehlen]
#13844: Jean-Pierre Flori: Let patch build on Cygwin on Windows 7
[Reviewed by Dmitrii Pasechnik]
#13888: Frédéric Chapoton: Barnette Sphere [Reviewed by Nathann Cohen]
#13908: Jeroen Demeyer: Exit Sage gracefully upon SIGHUP [Reviewed by
Volker Braun]
#13929: Thomas Feulner: Wrong comparison of sparse vectors [Reviewed by
Christian Nassau]
#13954: Jean-Pierre Flori: New Gap spkg (>=4.5) does not build with
shared only GMP/MPIR [Reviewed by Dmitrii Pasechnik]
#13958: Maarten Derickx: number of generators of number field ideal
blows up under multiplication [Reviewed by Marco Streng]
#13984: Nathann Cohen: Improve the is_vertex_transitive test [Reviewed
by Jernej Azarija]
#13988: Jeroen Demeyer: Run _write_started_file() only from sage-starts
[Reviewed by Volker Braun]
#13996: Jeroen Demeyer: Clean up spkg/bin/sage [Reviewed by Volker Braun]
#13998: Sébastien Labbé: hash of a pickled Sequence is broken [Reviewed
by Stephan Ehlen]
#14006: Viviane Pons: Bug with dumps() of Hasse diagrams [Reviewed by
Frédéric Chapoton]
#14008: Emmanuel Charpentier: Some R packages no longer can be
installed [Reviewed by Dmitrii Pasechnik]
#14022: François Bissey: Get scipy fortran objects be built with -fPIC
again [Reviewed by Jeroen Demeyer, Stephen Montgomery-Smith]
#14024: Volker Braun: More IPython 0.13 fixes [Reviewed by Keshav Kini]
#14027: Jeroen Demeyer: Disable sage-make_relative when upgrading
[Reviewed by Volker Braun]
#14028: Jeroen Demeyer: Fix "except:" statements [Reviewed by Volker Braun]
#14032: Jeroen Demeyer: determinant() of integer matrices of size in
[51,63] broken [Reviewed by Volker Braun]

[Nathann Cohen]

I still get the same crash as with beta2 :-/

sage: 

Exiting Sage (CPU time 0m0.01s, Wall time 0m0.47s).

*** glibc detected *** python: munmap_chunk(): invalid pointer: 0x00000000023fb550 ***

======= Backtrace: =========

/lib/x86_64-linux-gnu/libc.so.6(+0x76d76)[0x7f7340545d76]

/home/ncohen/.Sage/local/lib/libpython2.7.so.1.0(+0x8b17f)[0x7f734118917f]

======= Memory map: ========

00400000-00401000 r-xp 00000000 08:01 28574977                           /home/ncohen/.Sage/local/bin/python2.7

00600000-00601000 rw-p 00000000 08:01 28574977                           /home/ncohen/.Sage/local/bin/python2.7

0131a000-06218000 rw-p 00000000 00:00 0                                  [heap]

7f730c599000-7f730c59b000 r-xp 00000000 08:01 1317550                    /home/ncohen/.Sage/devel/sage-main/build/sage/libs/flint/flint.so

...

Nathann

[Ivan Andrus]

I built with SAGE_CHECK and SAGE_DEBUG off on OS X 10.8.2. I'm getting segfaults upon exit. Unfortunately, I'm about to move across the Atlantic and I won't have internet access for a few days.

sage:
Exiting Sage (CPU time 0m0.03s, Wall time 0m1.31s).
python(71762,0x7fff7315e180) malloc: *** error for object 0x7fbbcad5c8c0: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
------------------------------------------------------------------------
------------------------------------------------------------------------
Unhandled SIGABRT: An abort() occurred in Sage.
This probably occurred because a *compiled* component of Sage has a bug
in it and 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.
------------------------------------------------------------------------
./sage: line 135: 71762 Abort trap: 6 "$SAGE_ROOT/spkg/bin/sage" "$@"


Running under gdb was unhelpful (to me):

Reading symbols for shared libraries . done
sage:
Exiting Sage (CPU time 0m0.04s, Wall time 0m6.73s).
Reading symbols for shared libraries . done
python(71862,0x7fff7315e180) malloc: *** error for object 0x103e8a7a0: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

Program received signal SIGABRT, Aborted.
0x00007fff8b3c2212 in __pthread_kill ()
(gdb) thread apply all bt full

Thread 1 (process 71862):
#0 0x00007fff8b3c2212 in __pthread_kill ()
No symbol table info available.
#1 0x00007fff85fdaaf4 in pthread_kill ()
No symbol table info available.
#2 0x00007fff8601edce in abort ()
No symbol table info available.
#3 0x00007fff85ff2959 in free ()
No symbol table info available.
#4 0x00000001000542ff in dict_dealloc ()
No symbol table info available.


Also, the presence of a .gaprc file causes libgap initialization to fail. Initially I thought it was my particular .gaprc, but an empty file causes the same problem. I need to change to the new configuration files, but I thought I should mention this since there may be other users in a similar situation.


sage: import sage.libs.gap.libgap
---------------------------------------------------------------------------
RuntimeError Traceback (most recent call last)
<ipython-input-1-62de0029561d> in <module>()
----> 1 import sage.libs.gap.libgap

/Users/gvol/SageStuff/sage-5.7.beta2/libgap.pyx in init sage.libs.gap.libgap (sage/libs/gap/libgap.c:4149)()

/Users/gvol/SageStuff/sage-5.7.beta2/libgap.pyx in sage.libs.gap.libgap.Gap.__init__ (sage/libs/gap/libgap.c:2696)()

/Users/gvol/SageStuff/sage-5.7.beta2/local/lib/python2.7/site-packages/sage/libs/gap/util.so in sage.libs.gap.util.initialize (sage/libs/gap/util.c:3487)()

RuntimeError: libGAP initialization failed
#I You are using an old /Users/gvol/.gaprc file.
#I See '?Ref: The former .gaprc file' for hints to upgrade.


-Ivan

> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To post to this group, send email to sage-r...@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-release?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[John Cremona]

I am getting the same problem as I reported with beta1. The problem
is the "load" is triggering a DeprecationWarning : Use %runfile
instead of load.
See http://trac.sagemath.org/12719 for details.). As I have a load
command in my startup file (~/.sage/init.sage) this causes 3 tests to
fail, as does startup. I tried chnging the line in init.sage to read
"%runfile" instead of "load" but that did not work. Can someone who
knows about the ipython upgrade at #12719 please advise? The complete
contents of mt init.sage consists of only one line:

load /home/jec/sage/ecdb.py

John


%./sage
----------------------------------------------------------------------
| Sage Version 5.7.beta2, Release Date: 2013-01-31 |
| Type "notebook()" for the browser-based notebook interface. |
| Type "help()" for help. |
----------------------------------------------------------------------
**********************************************************************
* *
* Warning: this is a prerelease version, and it may be unstable. *
* *
**********************************************************************
---------------------------------------------------------------------------
NameError Traceback (most recent call last)
/home/jec/sage-5.7.beta2/local/lib/python2.7/site-packages/IPython/utils/py3compat.pyc
in execfile(fname, *where)
176 else:
177 filename = fname
--> 178 __builtin__.execfile(filename, *where)

/home/jec/.sage/init.sage in <module>()
----> 1 load /home/jec/sage/ecdb.py

NameError: name 'load' is not defined

[John Cremona]

On 1 February 2013 12:04, John Cremona <john.c...@gmail.com> wrote:
> I am getting the same problem as I reported with beta1. The problem
> is the "load" is triggering a DeprecationWarning : Use %runfile
> instead of load.
> See http://trac.sagemath.org/12719 for details.). As I have a load
> command in my startup file (~/.sage/init.sage) this causes 3 tests to
> fail, as does startup. I tried chnging the line in init.sage to read
> "%runfile" instead of "load" but that did not work. Can someone who
> knows about the ipython upgrade at #12719 please advise? The complete
> contents of mt init.sage consists of only one line:
>
> load /home/jec/sage/ecdb.py
>

Brief follow-up: after commenting out that line in init.sage, all
tests pass. And when I run sage from the command line, the load
command works fine. So it seems to me that there is a problem, in
that some tests are using "load" before whatever magic that we do to
make sage understand "load" has been set up, and that this problem is
seen when running tests in parallel.

John

[Kannappan Sampath]

Hello folks!

On this release, in SAGE_ROOT/devel/sage/sage/Symbolics/ , sage -t callable.py : 1 test fails. Not sure what has changed between this and the stable 5.6. On sage 5.6, all tests pass for this file.

Could someone confirm this?

[Michael Welsh]

On 1/02/2013, at 3:53 AM, Jeroen Demeyer <jdem...@cage.ugent.be> wrote:
>
> Please build, test, and report! We'd love to hear about your
> experiences with this release.

Not sure if this is relevant or not, but partway through the build (with -j10 -l10) I get the following error. There was a little load, but nothing I haven't built sage with in the past.

real 6m21.003s
user 8m52.277s
sys 0m23.522s
Successfully installed ntl-5.5.2.p0
Deleting temporary build directory
/Applications/sage-devel/spkg/build/ntl-5.5.2.p0
Finished installing ntl-5.5.2.p0.spkg
make[2]: INTERNAL: Exiting with 11 jobserver tokens available; should be 10!
make[1]: *** [all] Error 2

real 40m45.503s
user 169m2.184s
sys 15m42.831s
Error building Sage.
make: *** [build] Error 1

I'm running OS X 10.8.2 on a quad-core i7. I also got this error with beta1, though at a different place. Running make again, the build continues fine (as nothing actually failed to build)

[Jeroen Demeyer]

On 2013-02-03 22:44, Michael Welsh wrote:
> Finished installing ntl-5.5.2.p0.spkg
> make[2]: INTERNAL: Exiting with 11 jobserver tokens available; should be 10!
> make[1]: *** [all] Error 2

This looks like a bug in "make"

[kcrisman]

On Sunday, February 3, 2013 8:57:52 AM UTC-5, KnS wrote:

Hello folks!

On this release, in SAGE_ROOT/devel/sage/sage/Symbolics/ , sage -t callable.py : 1 test fails. Not sure what has changed between this and the stable 5.6. On sage 5.6, all tests pass for this file.

Could someone confirm this?

I'm sure you know the drill - what platform, specific doctest failure, etc.  At any rate it hasn't been reported all weekend. 

[Kannappan Sampath]

Oops, my bad! On ubuntu 12.04 64 bit (x86_64), here is what I get:

 

sage -t  "callable.py"                                      

**********************************************************************

File "SAGE_ROOT/sage-5.7.beta2/devel/sage-main/sage/symbolic/callable.py", line 87:

    sage: is_CallableSymbolicExpressionRing(CallableSymbolicExpressionRing((x,y,z)))

Expected:

    True

Got:

    False

**********************************************************************

1 items had failures:

   1 of   7 in __main__.example_1

***Test Failed*** 1 failures.

For whitespace errors, see the file /home/knsam/.sage//tmp/callable_15129.py

[1.6 s]

 

----------------------------------------------------------------------

The following tests failed:

sage -t  "callable.py"

Total time for all tests: 1.6 seconds

[Jean-Pierre Flori]

On Thursday, January 31, 2013 5:18:00 PM UTC+1, Nathann Cohen wrote:

I still get the same crash as with beta2 :-/

Do you mean beta1?

I get several crashes when setting MALLOC_CHECK_=3 and running "make ptestlong" on two different 64 bits Ubuntu 12.04.1 systems which horribly reminds me of what we had to deal with for ticket #715, e.g. doctesting sage/structure/parent.pyx yields a backtrace involving corce_dict.so, cachefunc.so and groebner_strategy.so.
Backtraces caused by other files look similar pointing to sage/libs/singular/groebner_strategy.pyx.
Ticket #12215 would look suspicious at this point.
But it does not happen with my 5.6 and 5.7.beta1 installs.
Maybe its just that our previous fix for groebner strategy was not robust enough and the inclusion of #12215 in beta1 and some random cosmic ray while I was downloading beta2 revealed the bug on my computers.
In fact I don't remember touching the file sage/libs/singular/groebner_strategy.pyx involved in this backtrace, so maybe a similar fix to the one we did before would be enough?
(I've set SAGE_DEBUG=yes but forgot that #13867 was not merged yet.)
(I must also complain that since #13889 I guess I cannot see any backtrace on screen because all my shell history is eaten by the memory map and the log file is quite empty because gdb cannot attachto the process thanks to Ubuntu default config, but note that the log does not include the printed backtrace and memory map.)

I also get timeouts for sage/groups/matrix_gps/matrix_group.py (without MALLOC_CHECK_ set).


Best,
JP

[Jeroen Demeyer]

I also tried ptestlong MALLOC_CHECK_=3 and get a crash in one place:

devel/sage/sage/graphs/generic_graph_pyx.pyx

This was introduced in sage-5.7.beta1, fixing this should be a blocker.

[Jean-Pierre Flori]

Strange you only get one.

I did not try "make ptestlong" with MALLOC_CHECK_=3 on 5.7.beta1.
I just tried the files which crashed on my 5.7.beta2 install and there were a bunch of them, I'd say ten or twenty.

[Simon King]

Hi,

On 2013-02-04, Jean-Pierre Flori <jpf...@gmail.com> wrote:
> I did not try "make ptestlong" with MALLOC_CHECK_=3 on 5.7.beta1.
> I just tried the files which crashed on my 5.7.beta2 install and there were
> a bunch of them, I'd say ten or twenty.

Strange that you even get *one* doctest right.

For me, sage-5.7.beta2 crashes on quitting Sage, when I build it with
SAGE_DEBUG=yes (and the fixes for the debug version stated in #13864).
This is *without* MALLOC_CHECK_.

What I get on exit is pasted below. I don't know if installing the gdb spkg
would give more info.

Cheers,
Simon

Exiting Sage (CPU time 0m2.70s, Wall time 0m28.45s).
Debug memory block at address p=0x1c8a6e0: API '�'
18302628885633695743 bytes originally requested
The 7 pad bytes at p-7 are not all FORBIDDENBYTE (0xfb):
at p-7: 0xcb *** OUCH
at p-6: 0xcb *** OUCH
at p-5: 0xcb *** OUCH
at p-4: 0xcb *** OUCH
at p-3: 0xcb *** OUCH
at p-2: 0xcb *** OUCH
at p-1: 0xcb *** OUCH
Because memory is corrupted at the start, the count of bytes requested
may be bogus, and checking the trailing pad bytes may segfault.
The 8 pad bytes at tail=0xfe00000001c8a6df are ------------------------------------------------------------------------
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libcsage.so(print_backtrace+0x31)[0x7f6de5c9d10d]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libcsage.so(sigdie+0x3d)[0x7f6de5c9d28f]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libcsage.so(sage_signal_handler+0x199)[0x7f6de5c9cae3]
/lib64/libpthread.so.0(+0xfd00)[0x7f6de91aed00]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(_PyObject_DebugDumpAddress+0x292)[0x7f6de9479ebe]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(_PyObject_DebugCheckAddressApi+0x114)[0x7f6de9479c1e]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(_PyObject_DebugFreeApi+0x36)[0x7f6de94798de]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(_PyObject_DebugFree+0x1d)[0x7f6de947978a]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/python2.7/site-packages/sage/rings/integer.so(+0x80292)[0x7f6dd6524292]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(_Py_Dealloc+0x35)[0x7f6de9477be4]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(+0xace8e)[0x7f6de9468e8e]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(_Py_Dealloc+0x35)[0x7f6de9477be4]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(+0xace8e)[0x7f6de9468e8e]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(_Py_Dealloc+0x35)[0x7f6de9477be4]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(_PyImport_Fini+0x80)[0x7f6de9531b45]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(Py_Finalize+0x58)[0x7f6de9545b86]
/home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libpython2.7.so.1.0(Py_Main+0xec1)[0x7f6de956276b]
python(main+0x20)[0x4007b4]
/lib64/libc.so.6(__libc_start_main+0xed)[0x7f6de87d223d]
python[0x4006d9]
------------------------------------------------------------------------
Attaching gdb to process id 17064.
gdb: Symbol `_Py_ZeroStruct' has different size in shared object, consider re-linking
gdb: Symbol `PyBool_Type' has different size in shared object, consider re-linking
gdb: Symbol `_Py_NotImplementedStruct' has different size in shared object, consider re-linking
gdb: Symbol `PyFloat_Type' has different size in shared object, consider re-linking
gdb: Symbol `_Py_TrueStruct' has different size in shared object, consider re-linking
gdb: Symbol `_Py_NoneStruct' has different size in shared object, consider re-linking

Saved trace to /home/simon/.sage/crash_logs/sage_crash_YBaPKm.log
------------------------------------------------------------------------
Unhandled SIGSEGV: A segmentation fault occurred in Sage.

This probably occurred because a *compiled* component of Sage has a bug
in it and 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.
------------------------------------------------------------------------

./sage: Zeile 135: 17064 Speicherzugriffsfehler "$SAGE_ROOT/spkg/bin/sage" "$@"

[Simon King]

Hi,

On 2013-02-05, Simon King <simon...@uni-jena.de> wrote:
> For me, sage-5.7.beta2 crashes on quitting Sage, when I build it with
> SAGE_DEBUG=yes (and the fixes for the debug version stated in #13864).
> This is *without* MALLOC_CHECK_.
>
> What I get on exit is pasted below. I don't know if installing the gdb spkg
> would give more info.

It does give more, but I don't really understand what to learn from the
backtrace below. At least, there are no weak references mentioned, which
always sounds like a good news to me, for some reason...

Cheers,
Simon

Stack backtrace
---------------

No symbol table info available.

#1 0x00007f9a7385d250 in print_enhanced_backtrace () from /home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libcsage.so

No symbol table info available.

#2 0x00007f9a7385d2c2 in sigdie () from /home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libcsage.so

No symbol table info available.

#3 0x00007f9a7385cae3 in sage_signal_handler () from /home/simon/SAGE/debug/sage-5.7.beta2/local/lib/libcsage.so

No symbol table info available.

#4 <signal handler called>

No symbol table info available.

#5 0x00007f9a77039ebe in _PyObject_DebugDumpAddress (p=0x1d5d660) at Objects/obmalloc.c:1649
q = 0x1d5d660 ""
tail = 0xfe00000001d5d65f <Address 0xfe00000001d5d65f out of bounds>
nbytes = 18302628885633695743
serial = 30791264
i = 0
ok = 1
id = -53 '\313'
#6 0x00007f9a77039c1e in _PyObject_DebugCheckAddressApi (api=111 'o', p=0x1d5d660) at Objects/obmalloc.c:1590
q = 0x1d5d660 ""
msgbuf = "bad ID: Allocated using API '\313', verified using API 'o'\000\000\000\000\000\000\000\000"
msg = 0x7fffaaef2030 "bad ID: Allocated using API '\313', verified using API 'o'"
nbytes = 28691032
tail = 0x67 <Address 0x67 out of bounds>
i = 32767
id = -53 '\313'
#7 0x00007f9a770398de in _PyObject_DebugFreeApi (api=111 'o', p=0x1d5d660) at Objects/obmalloc.c:1478
q = 0x1d5d650 "\375\377\377\377\377\377\377\377\313\313\313\313\313\313\313", <incomplete sequence \313>
nbytes = 28720288
#8 0x00007f9a7703978a in _PyObject_DebugFree (p=0x1d5d660) at Objects/obmalloc.c:1422
No locals.
#9 0x00007f9a641a9292 in __pyx_f_4sage_5rings_7integer_fast_tp_dealloc (__pyx_v_o=0x1d5d660) at sage/rings/integer.c:35775
__pyx_t_1 = 0
#10 0x00007f9a77037be4 in _Py_Dealloc (op=0x1d5d660) at Objects/object.c:2243
dealloc = 0x7f9a641a91c4 <__pyx_f_4sage_5rings_7integer_fast_tp_dealloc>
#11 0x00007f9a77028e8e in dict_dealloc (mp=0x1d9f680) at Objects/dictobject.c:985
ep = 0x1da38c8
fill = 25
#12 0x00007f9a77037be4 in _Py_Dealloc (op=0x1d9f680) at Objects/object.c:2243
dealloc = 0x7f9a77028d5b <dict_dealloc>
#13 0x00007f9a77028e8e in dict_dealloc (mp=0x673ba0) at Objects/dictobject.c:985
ep = 0x1c07048
fill = 277
#14 0x00007f9a77037be4 in _Py_Dealloc (op=0x673ba0) at Objects/object.c:2243
dealloc = 0x7f9a77028d5b <dict_dealloc>
#15 0x00007f9a770f1b45 in _PyImport_Fini () at Python/import.c:244
No locals.
#16 0x00007f9a77105b86 in Py_Finalize () at Python/pythonrun.c:470
interp = 0x602010
tstate = 0x6020a0
#17 0x00007f9a7712276b in Py_Main (argc=3, argv=0x7fffaaef2488) at Modules/main.c:664
c = -1
sts = 0
command = 0x0
filename = 0x7fffaaef3861 "/home/simon/SAGE/debug/sage-5.7.beta2/local/bin/sage-ipython"
module = 0x0
fp = 0x684a90
p = 0x0
unbuffered = 0
skipfirstline = 0
stdin_is_interactive = 1
help = 0
version = 0
saw_unbuffered_flag = 0
cf = {cf_flags = 0}
#18 0x00000000004007b4 in main (argc=3, argv=0x7fffaaef2488) at ./Modules/python.c:23
No locals.


Cython backtrace (newest frame = last)
--------------------------------------
#0 0x0000000000400794 in main()
#1 0x00007f9a771218aa in Py_Main()
#2 0x00007f9a77105b2e in Py_Finalize()
#3 0x00007f9a770f1ac5 in _PyImport_Fini()
#4 0x00007f9a77037baf in _Py_Dealloc()
#5 0x00007f9a77028d5b in dict_dealloc()
#6 0x00007f9a77037baf in _Py_Dealloc()
#7 0x00007f9a77028d5b in dict_dealloc()
#8 0x00007f9a77037baf in _Py_Dealloc()
#9 0x00007f9a641a91c4 in fast_tp_dealloc() at /home/simon/SAGE/debug/sage-5.7.beta2/devel/sage-main/sage/rings/integer.pyx:6053
6048
6049 # Free the object. This assumes that Py_TPFLAGS_HAVE_GC is not
6050 # set. If it was set another free function would need to be
6051 # called.
6052
> 6053 PyObject_FREE(o)
6054
6055
6056 hook_fast_tp_functions()
6057 from sage.misc.allocator cimport hook_tp_functions
#10 0x00007f9a7703976d in _PyObject_DebugFree()
#11 0x00007f9a770398a8 in _PyObject_DebugFreeApi()
#12 0x00007f9a77039b0a in _PyObject_DebugCheckAddressApi()
#13 0x00007f9a77039c2c in _PyObject_DebugDumpAddress()
#14 0x00007f9a77402a10 in __restore_rt()
#15 0x00007f9a7385c94a in sage_signal_handler()
#16 0x00007f9a7385d252 in sigdie()
#17 0x00007f9a7385d12b in print_enhanced_backtrace()
#18 0x00007f9a76d6e860 in waitpid()

[Michael Welsh]

It must have been. I upgraded the CLI (does anyone know of a way to get notified when such updates become available), and beta4 built just fine.