#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 jdemeyer):
Replying to [comment:24 kcrisman]:
> I also put in a print statement for bot and added
> {{{
> if pariOut:
> print "if pariOut worked"
> }}}
> after `pariOut` is first put in, and that printed and bot turned out to
be 2121924616. In case one cared :)
>
> But here is something perhaps slightly more interesting. If I print
before and after
> {{{
> init_stack(size)
> }}}
> I get `bot=0` before, but `bot=212...` after, but `bot=0` again by the
time the program segfaults.
`bot == 0` is certainly very bad and is surely the cause of the segfault.
It would be great if you could figure out why `bot` is set to zero.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11551#comment:26>
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.
