Issues and Workaround
When you are testing SPIDER we are particularly interested in feedback
about the following areas, listed in approximate order of priority:
- Crashing problems.
Any crashes or hangs in Eclipse or SICStus Prolog that occur when using
- Installation problems.
Any problems installing Eclipse or the SPIDER feature.
- Performance issues.
If SPIDER is slow or misbehaves for certain files or for large files
Note: The first thing to try if SPIDER is slow, is to increase the
memory allocated to Eclipse. See memory
issues, for more information.
- Broken or incomplete functionality.
If something does not work right.
Note that there are several
known incomplete features.
- Missing features.
If some must-have functionality is missing. Note that there are a
number of known missing features that we intend
- Other suggestions.
Any other feedback, including suggestions for new functionality, icon
design and other eye candy, etc.
This section will be updated with known issues.
Open Call Hierarchy does not
work for files that are not part of a project. A workaround is to
create a prolog project and add a link to your source directory, as
described under Work With
Existing Prolog Code.
Avoid symbolic links. Symbolic links can lead to all kinds of trouble,
especially when they create cycles. This is a problem with Eclipse and
not easily fixed in SPIDER.
The following is a list of features that are incompletely implemented
in the current release.
No support for conditional breakpoints. Only plain spypoints and line
breakpoints are supported.
^ command does not work in the debugger.
The Top level should have many of the Prolog-centric features of the Prolog editor,
like completion and documentation info-pops.
The following is a list of features that are missing that we hope will
be fixed ‘soon’. Please let us know what you miss!
The SPIDER Preferences should be improved and expanded.
The SICStus manuals etc. are already integrated with SPIDER but we
need more SPIDER-specific tutorials etc.
The Source Indexer will make SPIDER process all source code in the
project(s) by default. The default memory allocation for Eclipse
can be insufficient. This can cause Eclipse to be unresponsive
or to run out of memory.
SPIDER relies heavily on a cache that automatically adjusts to
available memory. If SPIDER runs slowly the best solution is, therefore,
to increase the memory allocated to Eclipse, see for instance The Eclipse FAQ or search for "eclipse
default memory" with your favorite search engine. Of course, the memory allocated to Eclipse
should be well below the amount of physical RAM in the machine.
As a last resort, it is possible to turn off the Indexer from the
preferences. The need to turn off the indexer should be considered a
bug in SPIDER so please report if you ever find it necessary to turn
off the indexer.
The following is a list of features, in no particular order, that we
want to add in future versions of SPIDER.
- Settings for the SICStus process.
It should be possible to use SPIDER to change various prolog flags,
debugger settings, working directory, etc.
- CLP debugger/visualizer.
Tools for debugging and visualizing Constraint Logic Programs (CLP) written