segfault when calling pOne() when currRing == NULL
jpflori · Thu Nov 20, 2014 6:50 pm
Hi all,
Still playing with Singular 3-1-7p1 in debug mode and Sage, we got a segfault when pOne gets called but currRing is not set.
With Singular 3-1-6 it was not the case.
See trac.sagemath.org/ticket/17184#comment:48 and following comments.
I think the following commit might explain the behavior change:
* bceefc05ad02b92a823faffb7a4a247a0da12fc0
Just removing the "#if 0" fixes our problem.
Though it surely is better to fix the issue and leave it there, or revert the whole commit.
Or should always make completely sure there is a currRing set?
Best,
JP
Still playing with Singular 3-1-7p1 in debug mode and Sage, we got a segfault when pOne gets called but currRing is not set.
With Singular 3-1-6 it was not the case.
See trac.sagemath.org/ticket/17184#comment:48 and following comments.
I think the following commit might explain the behavior change:
* bceefc05ad02b92a823faffb7a4a247a0da12fc0
Just removing the "#if 0" fixes our problem.
Though it surely is better to fix the issue and leave it there, or revert the whole commit.
Or should always make completely sure there is a currRing set?
Best,
JP