As I was looking for boolean simplification, I type )sh Expression Boolean. I get the list of the real expressions. So I type axiom sin (A::Expression Boolean) or true. Axiom disapproves >> System error: Caught fatal error [memory may be damaged]?... And the axiom process died the command-line after. cannot reproduce axiom process died --Bill Page, Mon, 27 Feb 2006 12:37:15 -0600 reply I can not reproduce your observation that:
the axiom process died the command-line after. This does not happen for me on at least the Windows version of Axiom. But I do find it very odd that Axiom allows the construction of
the domain axiom x:Expression Boolean:=true
Type: Expression(Boolean)
The scary sounding message: 'Caught fatal error [memory may be damaged]?' occurs for many operations applied to this object. The definition of the constructor axiom Boolean has OrderedSet
Type: Boolean
axiom true > false
Type: Boolean
although we might also question the wisdom of considering #271 )show Expression Boolean gives a list cannot reproduce axiom
process died --root, Fri, 03 Mar 2006 10:02:57 -0600 reply I've been running thousands of integrals thru axiom recently.
There is a problem related to interrupting Axiom while garbage
collection is running (I'm guessing) and, very occasionally,
Axiom will generate an error or die completely (only once so far).
However if Axiom is not interrupted I have yet to see it fail.
The "memory may be damaged" message occurs quite often but I have yet to see any surface damage on the DIMM packages :-). I'm not sure why Bill thought this was a reasonable error message but it does not seem to be a problem. Only console interrupts have caused failure so far and those seem to be related to some race condition in garbage collection. Tim Status: open => fix proposed Status: fix proposed => fixed somewhereno patch available http://fricas.svn.sourceforge.net/viewvc/fricas/trunk/src/interp/i-coerce.boot?r1=105&r2=189&view=patch |