Project

General

Profile

Bug #1383

NewPolyRing on MS Windows

Added by John Abbott over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
John Abbott
Category:
bug
Target version:
CoCoA-5.3.0
Start date:
07 Jan 2020
Due date:
% Done:

100%

Estimated time:
0.99 h
Spent time:
1.00 h

Description

Bernhard Andraschko reports that the following causes a crash on MS Windows 10 Pro (10.0.17763)

define BernhardBug()
  S := NewPolyRing(RingQQ(), SymbolRange("x",[1,1],[3,3]));
  return S;
enddefine; -- BernhardBug

BernhardBug();

Related issues

Related to CoCoA-5 - Bug #1384: NewPolyRing and SymbolRangeClosed2020-01-07

History

#1 Updated by John Abbott over 4 years ago

JAA says the bug is not present on current internal version of CoCoA-5 compiled and running on Linux.

The error message is produced by a failed BOOST assertion about a pointer being NULL when it should not be.
Bernhard will send more details in another comment.

#2 Updated by John Abbott over 4 years ago

  • Description updated (diff)

#3 Updated by John Abbott over 4 years ago

  • Description updated (diff)

#4 Updated by John Abbott over 4 years ago

  • Related to Bug #1384: NewPolyRing and SymbolRange added

#5 Updated by John Abbott over 4 years ago

In any case we should add an example like this as a new "official" test.

#6 Updated by Bernhard Andraschko over 4 years ago

The error code displayed after calling the function BernhardBug() is

assertion "px != 0" failed: file "/usr/include/boost/smart_ptr/intrusive_ptr.hpp", line 161, function: T* boost::intrusive_ptr<T>::operator->() const [with T = CoCoA::InterpreterNS::INT]

The problem is that NewPolyRing can't handel the output of SymbolRange and it appeared with any coefficient ring I tried.
Actually, after updating we found out that this seems to be fixed in CoCoA-5.2.5 (also on Windows). The bug only appeared in version 5.2.4.

#7 Updated by John Abbott over 4 years ago

  • Status changed from New to Resolved
  • Assignee set to John Abbott
  • % Done changed from 0 to 50

Can we now close this issue as it seems to be completely resolved using the latest release of CoCoA-5?
Anyway, a test should be added to exbugs.cocoa5; perhaps I can do that. DONE checked into CVS.

Does the problem persist on Linux using the latest version?

#8 Updated by Bernhard Andraschko over 4 years ago

According to Peter Mader it also works on Linux with this version, so I think we can close this thread.

#9 Updated by John Abbott over 4 years ago

  • Target version changed from CoCoA-5.4.0 to CoCoA-5.3.0
  • % Done changed from 50 to 90
  • Estimated time set to 0.99 h

Both Bernhard and Peter confirm that everything is fine using the "interim" release 5.2.5; they did comment that the web site suggested that 5.2.4 is "more reliable" than 5.2.5... in this case that advice is misleading!

Moving to Feedback.

#10 Updated by Anna Maria Bigatti over 4 years ago

I confirm it works fine on MacOS.

#11 Updated by Anna Maria Bigatti over 4 years ago

  • Status changed from Resolved to Feedback

#12 Updated by Anna Maria Bigatti about 4 years ago

  • Status changed from Feedback to Closed
  • % Done changed from 90 to 100

Also available in: Atom PDF