The recent multitasking discussion brings out how difficult it is to debug even simple things such as unexpected stack actions when the functions are in a different thread/callback. While SLEEP could have been tried within the Forth console window, not all functions (callbacks especially) can be invoked manually. Event messages might be an example.

Does anyone have any debugging tips that have helped them debug code in callbacks and other threads? I've resorted, in some cases, to writing stuff to log files, and find this awkward and time consuming compared to debugging from the forth console. One of the real problems is that I can't confirm through testing that my callback code is bug-free--there may be a problem lurking in there, but I can't easily set up callback conditions to reveal it.

Help, anyone?

Glenn Dixon
  
Received on Wed Jul 05 2000 - 08:09:14 PDT