Debugging with Borland Delphi

When the Delphi IDE has been started using DbgShell, its integrated debugger is automatically configured to act as a cross debugger for On Time RTOS-32. In general, cross debugging within Delphi works exactly the same way as native debugging.

Before debugging, make sure the active project is set to the console .exe project of the project group and that the whole project group is up-to-date. Unfortunately, the Delphi IDE does not automatically rebuild a project group before a debug session is started. Thus, before you debug, save all editor files and then invoke menu command Project|Compile All Projects or Build All Projects. Then use any Delphi menu command to start a debug session (e.g., step into, etc.). The program will be downloaded to the target and all of the Delphi debugger features are available. Please note that the project should not be configured for remote debugging within Delphi. Redirecting the debugger is performed by DbgShell and not by Delphi.

When the target is suspended at a breakpoint, the debugger's context is set to the current thread. If you need to inspect another thread's local variables, set a breakpoint in that thread and run to that breakpoint. Global data is always accessible in the debugger, regardless of the current thread.

Left Using Borland Delphi

Setting up a Project (Delphi 2007)