Debugging delivered app - differences between LWW4.4.6 and LWW5.0?

Hi,

I have a small CAPI app on LWW which runs a gui in one thread and one or
more worker threads.

After moving it over to LWW5.0 I ran into a problem trying to diagnose a
problem with the delivered app.
One of the worker threads was throwing an error trying to access a
missing DLL (part of the app).  The error was reported in a console
window, but the app immediately quit without giving me the chance to
even read it.  Provoking the same error on the LWW4.4.6 build produced
the console window but did not kill the app - enabling me to debug the
problem.

Both apps are built from identical sources with the same delivery
script, the salient features of which are:

(deliver 'app::run "app" 0
         :keep-debug-mode :keep-packages
         :warn-on-missing-templates t
         :interface :capi
         :format t
         :keep-conditions :all
         :keep-clos t
         :keep-editor t
         :keep-lisp-reader t
         :keep-symbols '(COMMON-LISP::NIL))

Is there something else I need to do with LWW5.0 to prevent the app
dying when the worker thread generates an error?

- Dominic

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________