#10018: Unhandled SIGSEGV after bnfcertify()
------------------------+---------------------------------------------------
Reporter: jdemeyer | Owner: tba
Type: defect | Status: new
Priority: critical | Milestone: sage-4.6
Component: c_lib | Keywords: segfault segmentation fault bnfcertify
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Description changed by jdemeyer:
Old description:
> Do the following in Sage:
> {{{
> sage: K.<z> = CyclotomicField(23); bnf=K.pari_bnf(certify=False)
> sage: bnf.bnfcertify()
> }}}
> After typing the second line {{{bnf.bnfcertify()}}}, hit CTRL-c after 10
> seconds or so. It will take a long time before the interrupt registers,
> but eventually a KeyboardInterrupt will show up. However, something is
> wrong after this KeyboardInterrupt, because typing
> {{{
> K.<z> = CyclotomicField(23)
> }}}
> immediately gives the dreaded
> {{{
> ------------------------------------------------------------
> Unhandled SIGSEGV: A segmentation fault occurred in Sage.
> This probably occurred 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).
> ------------------------------------------------------------
> }}}
New description:
Do the following in Sage:
{{{
sage: K.<z> = CyclotomicField(23); bnf=K.pari_bnf(certify=False)
sage: bnf.bnfcertify()
}}}
After typing the second line {{{bnf.bnfcertify()}}}, hit CTRL-c after 5
seconds or so (not immediately). It will take a long time before the
interrupt registers, but eventually a KeyboardInterrupt will show up.
However, something is wrong after this KeyboardInterrupt, because typing
{{{
K.<z> = CyclotomicField(23)
}}}
immediately gives the dreaded
{{{
------------------------------------------------------------
Unhandled SIGSEGV: A segmentation fault occurred in Sage.
This probably occurred 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).
------------------------------------------------------------
}}}
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10018#comment:1>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
