Debuggers

INtime executables run independently of Windows executables in separate virtual machines, so debugging is a straight-forward process. Two INtime real-time debuggers are available: Spider and an integrated Visual Studio debugger. Both incorporate a Windows-based GUI to simplify and speed the debugging process. The net result is a familiar full source-level debugging environment that never requires simulation of the real-time run-time environment; you debug applications at full-speed in the environment in which they will be deployed. This configuration also allows you to simultaneously debug Windows executables and real-time executables and model their interaction.

Integrated Visual Studio Real-time Debugger and Fault Manager

The INtime real-time development environment is fully integrated into Visual Studio 2003 and 2005. You can edit, compile, link, debug, and trap process faults without leaving the Visual Studio development environment. If a real-time programming error generates a CPU exception the faulted real-time thread is suspended, giving you the option of starting the Visual Studio debugger at the precise point of exception; non-related processes and threads in the system continue to run without interruption. Real-time process faults can result from divide by zero errors, bad pointer accesses, page faults, stack faults, and other CPU exceptions.

The INtime real-time debugger plug-in for Visual Studio gives you this unique ability to monitor real-time variables, debug real-time processes, and capture real-time faults directly from within the Visual Studio debugger. INtime software includes full access to breakpoints, source-level single-stepping, and watch variables for real-time processes and threads, all from within the familiar Visual Studio development environment, eliminating the need to master a second set of development tools.

Real-time Process Fault Manager

Because INtime real-time applications run in user-mode, or ring 3, they can be easily trapped and suspended in the event of a processor fault due to hidden programming errors, such as a divide by zero or null pointer. Only the faulted real-time process is suspended, all other real-time and Windows processes continue to run normally. Like the Windows fault manager, the INtime real-time fault handler gives you the option of terminating the faulted real-time process or breaking directly into the INtime source-code debugger at the point of the fault condition.