Post a reply
Note:If not registered, provide any username. For more comfort, register here.
Message body:
Enter your message here, it may contain no more than 60000 characters. 

:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:
Font size:
Font colour
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Disable BBCode
Disable smilies
Do not automatically parse URLs
Confirmation of post
To prevent automated posts the board requires you to enter a confirmation code. The code is displayed in the image you should see below. If you are visually impaired or cannot otherwise read this code please contact the %sBoard Administrator%s.
Confirmation code:
Enter the code exactly as it appears. All letters are case insensitive, there is no zero.

Topic review - segfault when calling pOne() when currRing == NULL
Author Message
  Post subject:  Re: segfault when calling pOne() when currRing == NULL  Reply with quote
Thanks, that's exactly what I did!
Post Posted: Mon Nov 24, 2014 4:26 pm
  Post subject:  Re: segfault when calling pOne() when currRing == NULL  Reply with quote
All of the polynomial routines require a ring, as argument or via the global variable currRing. If such a ring does not exit, an error should be reported.
The problem here is the place to check this: 3-1-6 does it during the resolution
of reserved names (IsCmd) while 4-0-0 should check during the evaluation of expressions.
The easiest way to fix it is really to change the "#if 0" to "#if 1" as the check during the evaluation is missing and also not necessary for 3-1-7.
Post Posted: Fri Nov 21, 2014 6:54 pm
  Post subject:  segfault when calling pOne() when currRing == NULL  Reply with quote
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 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?

Post Posted: Thu Nov 20, 2014 6:50 pm

It is currently Wed Apr 08, 2020 10:41 pm
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group