Recently, Leif and I have been trying to track down #11551 (Pari
segfaults on startup in Cygwin).
The problem occurs in a (to me) odd spot. Namely, in sage/misc/
functional.py, there is an import of CDF. Print statements show that
- all inside this one line! - we initialize PariInstance, go to
integer.pyx for the first time, and lots of other stuff.
The problem is that all of these things happen BEFORE ANY print
statements in complex_number.pyx! Looking at complex_number.c, it
becomes clear that this is because Cython puts a lot of cimport and
other stuff long before the "regular" stuff in the C file.
But I don't know enough about the order that these things happen in,
nor how to tell that from the C file, to trace it all out. Can
someone give me a sense - or show me enough of how to do it so I can
do it myself - how to track what's being done in complex_number.
{pyx,c} so I can tell what modules to try debugging? The Pari stack
is good in the whole of gen.pyx, and somehow has been corrupted by
integer.pyx, so it would suffice to know what is imported between
them.
As a side note, following the sage imports in sage/all.py is a
nightmare. A whole bunch of the stuff supposedly imported later is
already imported right away, because we import sage/misc/all.py really
early on, which imports most functions from sage/misc/functional.py -
and that imports quite a bit of "main" Sage.
Much thanks in advance - we are definitely making progress, and would
value the additional support.
- kcrisman
--
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
