Under 'Urgency' tell us how urgent the issue is for you. We classify reports as follows:
A bug or missing feature that is stopping progress. Probably needs a private patch, possibly under a support contract, unless a workaround can be found.
Either a fix in the next patch bundle or as a private patch, possibly under a support contract.
A fix would be nice in the next minor release.
An item for our wishlist.
Probably not a bug or feature request.
Tell us if the bug is repeatable. Add instructions on how to reproduce it to the 'Description' field of the bug report form.
Include any other information you think might be relevant. This might be your code which triggers the bug. In this case, please send us a self-contained piece of code which demonstrates the problem (this is much more useful than code fragments).
Include the output of the Lisp image. In general it is not useful to edit the output, so please send it as-is. Where output files are very large (> 2MB) and repetitive, the first and last 200 lines might be adequate.
If the problem depends on a source or resource file, please include that file with the bug report.
If the bug report falls into one of the categories below, please also include the results of a backtrace after carrying out the extra steps requested:
t, and try again.
erroror conditions or related functionality, trace
conditions:coerce-to-condition, and try again.
niland try again. This will cause the console version of debugger to be used instead.
toggle-source-debugging nil) and try again.
<**>, please send all of the output--however much there is of it.
terminal output is that written to
. Normally this is not visible when running the Mac OS X native GUI or the Windows GUI, though it is displayed in a Terminal.app or MS-DOS window if necessary.
LispWorks Release Notes and Installation Guide - 23 Dec 2011