On Jan 26, 4:05 pm, Simon King <[EMAIL PROTECTED]> wrote:
> Dear Sage developers,
Hi Simon,
> the three lines of code below produce a segmentation fault. Shall i
> open a ticket?
Yep, please do so. libSingular is not surprisingly involved:
(gdb) bt
#0
__pyx_pf_4sage_5rings_10polynomial_34multi_polynomial_ideal_libsingular_interred_libsingular
(
__pyx_self=<value optimized out>, __pyx_v_I=0x2af2cff2eaf0)
at sage/rings/polynomial/multi_polynomial_ideal_libsingular.cpp:
3059
#1 0x0000000000484326 in PyEval_EvalFrameEx (f=0x1a6a310,
throwflag=<value optimized out>) at Python/ceval.c:3552
#2 0x000000000048403b in PyEval_EvalFrameEx (f=0x1a623a0,
throwflag=<value optimized out>) at Python/ceval.c:3650
#3 0x0000000000484f3b in PyEval_EvalCodeEx (co=0x2af2c2b2db70,
globals=<value optimized out>,
locals=<value optimized out>, args=0x2af2cff25380, argcount=2,
kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0)
at Python/ceval.c:2831
#4 0x00000000004ce528 in function_call (func=0x2af2c2b36cf8,
arg=0x2af2cff25368, kw=0x0) at Objects/funcobject.c:517
#5 0x0000000000415523 in PyObject_Call (func=0x1a6b890, arg=0x1,
kw=0x7fffefddfec0) at Objects/abstract.c:1860
#6 0x000000000041bc43 in instancemethod_call (func=<value optimized
out>, arg=0x2af2cff25368, kw=0x0)
at Objects/classobject.c:2497
#7 0x0000000000415523 in PyObject_Call (func=0x1a6b890, arg=0x1,
kw=0x7fffefddfec0) at Objects/abstract.c:1860
#8 0x000000000047c851 in PyEval_CallObjectWithKeywords
(func=0x2af2cf8c4320, arg=0x2af2cf8a5d50, kw=0x0)
at Python/ceval.c:3433
Once you open the ticket I will attach a backtrace. Might this just be
a missing error check for a corner case?
> Yours
> Simon
Cheers,
Michael
> ----------------------------------------------------------------------
> | SAGE Version 2.10, Release Date: 2008-01-18 |
> | Type notebook() for the GUI, and license() for information. |
> ----------------------------------------------------------------------
>
> sage: R=PolynomialRing(QQ,'x,y,z')
> sage: I=R.ideal()
> sage: I==R.ideal()
>
> ------------------------------------------------------------
> 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).
> ------------------------------------------------------------
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
