Re: [sage-devel] Threading and cypari

The problematic bullet point in that PR is: * Don't copy everything from the PARI stack. During the 2018 PARI/GP atelier, I talked to Karim Belabas about a strategy to achieve this. The basic idea is that we need to have a linked list containing the Gens which live on the PARI stack. When the t

Re: [sage-devel] Threading and cypari

This is commit 551a5277456a3170dd690773e22f319cc1ad795a from https://github.com/sagemath/cypari2/pull/59. On Thu, 14 Nov 2024 at 09:13, David Roe wrote: > > Thanks for the suggestion. Is there a PR when cypari2 started using pointers > on the PARI stack? I'm just trying to figure out how to ma

Re: [sage-devel] Threading and cypari

Thanks for the suggestion. Is there a PR when cypari2 started using pointers on the PARI stack? I'm just trying to figure out how to make such a change. David On Thu, Nov 14, 2024 at 2:44 AM Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Hi David, > > I think that a reasonable move is t

Re: [sage-devel] Threading and cypari

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 wrote: > > This bug is continuing to seriously impact the LMFDB. We haven't had a > functional

Re: [sage-devel] Threading and cypari

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 interf

Re: [sage-devel] Threading and cypari

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) o

Re: [sage-devel] Threading and cypari

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. Best Vincent

[sage-devel] Threading and cypari

Upgrading Sage from 9.2 to 9.3 breaks the LMFDB (segfaults on startup). We believe that the problem arises from an interaction between Pari and threads, and were able to duplicate it in Sage with the following: from concurrent.futures import ThreadPoolExecutor sage: with Th