The KPML documentation

Troubleshooting
next
up previous
contents
index
Next: Computational Systemic-Functional Linguistics Up: Introduction Previous: Known
bugs/problems
Troubleshooting
If serious errors occur during the loading of Loom, check that Loom has been previously compiled.
KPML will not try to compile Loom itself, but loading a noncompiled Loom version will fail.
If installation appears to have been completed successfully, but examples do not generate the intended
strings, then some component of the lingusitic resources has not been loaded appropriately. There are
some systematic failures that can be indicative of particular causes. Most typical is that all SPL inputs
result only in nominal phrases being generated: this is usually due to the Upper Model not having
been loaded during the configuration phase.
If Emacs and Allegro Common Lisp are not being used, then error conditions can cause more than
one process to use the originating Lisp listener simultaneously! The user must ensure that the required
input makes it way to the appropriate process (e.g., by repeating it until accepted).
If the interface is up and running but after selection of some command it stops reacting, then check:
1. that all of the KPML windows are `open' or `expanded'--if a window is `closed' or `iconized',
menus dependent on that window will not be brought up until the window is open;
2. that no error condition (e.g., a network or X-server fault) has thrown control back to the calling
Lisp process.
It is possible that some unfortunately syntactically misformed resource definitions that escape
detection on loading can bring the interface to a halt if a request is made to inspect them. Since
inspection can only take place in the Inspector window (Chapter 6), it is generally only this window
that is affected. Should this occur, there is no available option for continuing, and control-Z from the
interface fails to abort, then the Inspector can be restarted by typing at the originating Lisp listener (cf.
Section 14.6):
next
(kpml-i::startup-resource-inspector-frame T)
up previous
contents
index
Next: Computational Systemic-Functional Linguistics Up: Introduction Previous: Known
bugs/problems
http://www.darmstadt.gmd.de/publish/komet/kpml-1-doc/node13.html (1 von 2) [11.12.2004 14:20:21]