Bugs and Limitations Status

Thread View: fj.mail-lists.reduce

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Minaz Punjani Thu, 02 Jul 1992 15:48

#116

Author: Minaz Punjani
Date: Thu, 02 Jul 1992 15:48

34 lines
1771 bytes

Dear Reduce Users and Developers,

Some users of Reduce at ULCC are encountering bugs and limitations
in Reduce. The following are some of the error messages

***** Segmentation Violation in >COPYFROMSTACK<+0x192

***** Fatal error: Error not within ErrorSet

***** Factorizer error: Content divison in GCDLIST3 failed

Other error messages I am aware (User's Guide for Convex C200
Computers) of include:

          Floating point exception.

          Heap space exhausted.

          Non-numeric argument in arithmetic.

          Segmentation violation.

          Bus error.

          Binding stack overflow starting.


Is there a comprehensive bugs and limitations list available in Reduce? 
Are folk interested in a regular bugs and limitation list?

I look forward to your comments through this august forum.

Minaz Punjani
Engineering Computing and SENAC Coordinator.

Bugs and Limitations Status

#121

Author: F.J.Wright
Date: Wed, 15 Jul 1992 16:53

27 lines
2483 bytes

It seems to me that almost all of the error messages that M. Punjani listed
are not what I would regard as REDUCE error messages, but are coming from
the underlying Lisp, which I assume is PSL.  The factorizer error looks
like a real REDUCE error, and is very similar to one that we managed to
provoke here, but I know what caused it here (a bug in some code of mine).
Usually, when I see error messages like those listed they can be traced to
some user having done something silly in symbolic mode.

I think there is some scope for confusion, because either REDUCE emulates
PSL error messages or vice versa, so it is not obvious what level they come
from.  By contrast, CSL precedes its error messages by + signs, so avoiding
this problem, and probably other Lisps have other conventions also.  But
perhaps most users don't care what level error messages come from anyway!

There used to be a bug list for REDUCE 3.3, but I don't recall seeing one
for 3.4.  For myself, I would probably be interested to see reports of bugs
and limitations that are generic (not Convex-specific) as long as they are
well isolated and can be described in less than about 25 lines (one
"standard" screenful).  It is quite possible that somebody has already
fixed a particular bug, or may feel inclined to fix it quickly, if it is
brought to their attention.  (I mean other than the developers, who seem
pretty good at doing this already.)  Also, fixes and enhancements appear in
the network library from time to time.  For example, an improved version of
the Groebner package has been available for some time.

Francis
F.J.Wright@QMW.ac.uk

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads