Hi David,

I think that a reasonable move is to revert the use of pointers on the
PARI stack. It created a lot of trouble with memory management.

Best
Vincent

On Thu, 14 Nov 2024 at 04:21, David Roe <roed.m...@gmail.com> wrote:
>
> This bug is continuing to seriously impact the LMFDB.  We haven't had a 
> functional debugger for 3 years.  It's preventing us from serving large 
> downloads, limiting users' ability to download large search results.  Today, 
> it's interfering in efforts to add the Stein-Watkins and BHKSSW elliptic 
> curve databases to the LMFDB, since the files they contain are too large to 
> host with a non-threaded 30 second timeout.
>
> Help resolving the bug or suggesting workarounds is welcome.
> David
>
> On Fri, Jun 4, 2021 at 3:54 PM David Roe <roed.m...@gmail.com> wrote:
>>
>>
>>
>> On Fri, Jun 4, 2021 at 3:24 PM Vincent Delecroix <20100.delecr...@gmail.com> 
>> wrote:
>>>
>>> Thread support in cypari2 is definitely a reasonable requirement.
>>> I don't think this is tested.
>>>
>>> It would be nice to
>>>
>>> 1) reproduce the segfault outside of sage only using python and
>>>     cypari2
>>>
>>> 2) open an issue on cypari2 development website at
>>>     https://github.com/sagemath/cypari2.
>>
>>
>> Thanks.  I've made https://github.com/sagemath/cypari2/issues/107.
>> David
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion visit 
> https://groups.google.com/d/msgid/sage-devel/CAChs6_m6a1akrUuX2s7dObcDJQ-jpH3WMZQauD8b3s00Xg0%3Dtw%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAk_sjON0uYO3gAmt3VsbaY69qMvFqVZnm_PtGPuEgKD-g%40mail.gmail.com.

Reply via email to