#20463: Pari segfault on Sage startup in Cygwin (2)
-------------------------------------+-------------------------------------
Reporter: embray | Owner:
Type: defect | Status: needs_work
Priority: major | Milestone: sage-7.3
Component: porting: Cygwin | Resolution:
Keywords: cygwin windows | Merged in:
Authors: Erik Bray | Reviewers:
Report Upstream: Reported | Work issues:
upstream. No feedback yet. | Commit:
Branch: u/embray/pari- | fcc10fc6cebcfb92ac71207099f80fa120afb04d
mmap-cygwin | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Description changed by jdemeyer:
Old description:
> This is the same issue as #11551, but as that issue was closed several
> years ago (with no satisfying resolution) it was suggested I open a new
> ticket. The code has changed a little bit since then too. Most notably
> as of
> [http://git.sagemath.org/sage.git/commit/src/sage/libs/pari/decl.pxi?h=develop&id=ade4f7521ad77c03e9791bc3768d9a9e3a2daca4
> ade4f752] there are no longer `bot`, `top` and `avma` global variables in
> `paridecl.pxi` (then `decl.pxi`). Now there is a single struct
> `pari_mainstack` with these pointers as elements. I don't think that
> makes an enormous difference though, but it does change the discussion
> somewhat.
>
> Otherwise the !Python/Cython level stacktrace is almost the same as
> before. The segfault occurs on
> [http://git.sagemath.org/sage.git/tree/src/sage/rings/real_mpfr.pyx?h=976c0f3d0f9f0ac744e535ea734dadf2e7918991#n3138
> this line] which I guess happens to be reached the first time any PARI
> object is created during import. I haven't debugged deeper than that yet
> but I'm guessing it's the same issue as in the original ticket--that the
> PARI stack somehow hasn't been initialized yet.
>
> [Incidentally, one thing that did seem to work is cysignals--it caught
> the segfault and raised a Python exception for it. So I don't *think*
> cysignals is related here but I wouldn't necessarily rule it out either.]
New description:
Due to a Cygwin bug https://cygwin.com/ml/cygwin/2016-05/msg00140.html
there is a segmentation fault when the PARI maximum stack size is larger
than 4GB.
--
--
Ticket URL: <http://trac.sagemath.org/ticket/20463#comment:8>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
