#12173: Update FLINT to 2.3
-------------------------------+--------------------------------------------
Reporter: mhansen | Owner: tbd
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.1
Component: packages | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: #12433 | Stopgaps:
-------------------------------+--------------------------------------------
Comment (by jpflori):
Replying to [comment:52 fredrik.johansson]:
> I do think moving the _fmpz_cleanup call within quit_sage is the correct
solution if it does work.
I'm quite ok with this decision, although, as I pointed before, I have no
idea of when Python/Sage objects actually get deallocated, so this might
be a flaky solution.
Now I'm getting a little lost:
I have trouble to understand how the error (in the different forms it
takes, I assumed it was actually an underlying "double free") can be
caused by a call to fmpz_poly_clean after _fmpz_cleanup was called.
Indeed, all fmpz_poly_clean does is to deallocate the space needed to
store pointers to the coefficients and write in the fmpz_unused_arr that
the coeff itself can be reused.
This array was already deallocated by _fmpz_cleanup, so we end up writing
somewhere we should not really, but whatever should I say: it is quite
unlikely that this will actually break something.
Sorry if that sounds stupid or is deeply wrong, but I prefer to be sure
everything is clear in my mind.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12173#comment:53>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
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-trac?hl=en.
