#11551: Pari segfault on Sage startup in Cygwin
------------------------+---------------------------------------------------
Reporter: kcrisman | Owner: tbd
Type: defect | Status: new
Priority: major | Milestone: sage-4.7.2
Component: cygwin | Keywords: pari
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
------------------------+---------------------------------------------------
Comment(by kcrisman):
Okay, inserting appropriate print statements gives
{{{
Got to first line of PariInsstance init
Got beyond 'if bot' of PariInstance init instead
Got beyond 'pari_init_opts'
Got here
Got to just before pari_float
}}}
which can be interpreted as
* Pari was initialized
* the 'if bot' was NOT taken
* and `pari_init_opts` was apparently called
* then we got to the complex number line
* then we got to the `real_mpfr` line with the `cgetr`
* and we didn't make it past that, as usual.
So apparently `bot` was not yet set, contrary to your hypothesis, but
there is still something weird going on with the stack. The rest of the
lines in the `_init_` don't look that innocent either; if one of them
failed or allocated something null would it raise an error? (Like the
`pari_free` line or the `pariOut` lines?)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11551#comment:23>
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.
