On 1 February 2012 21:00, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> On 2012-02-01 21:31, John Cremona wrote:
>> On investigating #12403 I discovered this serious bug (version 4.8):
>>
>> sage: pari.default('parisize')
>> 16000000
>> sage: pari.default('parisize',32000000)
>> *** Warning: new stack size = 32000000 (30.518 Mbytes).
>> *** Error in the PARI system. End of program.
>>
>> so increasing the stacksize of the pari library crashed Sage stone
>> dead. Is this known?
> It is not known but it's not surprising given that Sage takes care of
> the PARI stack. In Sage, you can use
>
> sage: pari.allocatemem(10^7)
> sage: pari.default('parisize')
> 10000000
>
> But that should never be needed, since Sage automagically increases the
> PARI stack as needed.
That is what I had thought. But the code at #12403 causes a crash,
which I have been assuming was because of too small a stack. It may
be that there is a different error. Using pari.allocatemem() as you
suggest, there is still an error raised using the code at #12403.
So as well as the problem at that ticket we now have a second one; why
pari.default() causes a crash.
John
>
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this group, send an email to
> sage-devel+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
