Running the OSI debugger
How to use the OSI debugger in detail is described in the "ODABA Script Interface" user's guide. Since context functions are called from within the database system or GUI framework, one cannot step directly into a certain context function. Instead, it is suggested to set a breakpoint in order to stop processing as soon as the breakpoint has been reached.
Since ODABA GUI applications run in the ODABA GUI frame work, which redirects system output to the application output area, it requires a some additional steps in order to debug OSI GUI applications.
- Call code.exe instead of ode.exe. code.exe is a command line version for running GUI applications in a console.
- In order to call code.exe, the section name in the configuration or ini-file for the application has to be changed from [ode] to [code].
- Set CONSOLE_APPLICATON=YES in the applications configuration file. This will redirect output from the application output area to console.
- Set break points in OSI functions, where the application should halt for further investigation.
When not setting CONSOLE_APPLICATION, the system context is directed to the application rather than to the console and no input is possible via console. This may cause your application waiting forever, as soon as the OSI debuger requires input.