On Apr 23, 5:51 am, "Georg S. Weber" <georgswe...@googlemail.com>
wrote:
> Hi Michael,
Hi Georg,
> probably you did. But just to be sure: did you really do tests with
> the singular spkg I put a while ago at
> http://sage.math.washington.edu/home/weberg/spkg/
> ?
Your spkg + sage -b to rebuild the extensions blow up in exactly the
same fashion as what is in Sage 3.4.1:
bash-3.2$ ./sage
----------------------------------------------------------------------
| Sage Version 3.4.1.rc4, Release Date: 2009-04-19 |
| Type notebook() for the GUI, and license() for information. |
----------------------------------------------------------------------
Memory manager stolen back
Closing handle
MPolynomialRing_generic.__init__
Doing: <char**>omAlloc0(sizeof(char*)*(len(self._names)))
Done: <char**>omAlloc0(sizeof(char*)*(len(self._names)))
Allocating ring ...
------------------------------------------------------------
Unhandled SIGSEGV: A segmentation fault occured in SAGE.
This probably occured because a *compiled* component
of SAGE has a bug in it (typically accessing invalid memory)
or is not properly wrapped with _sig_on, _sig_off.
You might want to run SAGE under gdb with 'sage -gdb' to debug this.
SAGE will now terminate (sorry).
------------------------------------------------------------
The above messages should be clear once you look into
multi_polynomial_libsingular.pyx.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
