QNX RTOS v4 Knowledge Base
QNX RTOS v4 Knowledge Base
| Title |
Available system-level debugging tools for QNX4 |
| Ref. No. |
QNX.000000600 |
| Category(ies) |
Development |
| Issue |
Areas of interest for system-level debugging tools in QNX4 to cover are:
-source-level debuggers that work within interrupt handlers
- tools that would allow breaking into a "hung" system
- debug output functions for doing printf style formatted output to serial ports to be captured by external equipment. Also tools that allow viewing of a core dump would be useful.
|
| Solution |
Debugger32 is a low-level 32-bit system debugger. It must be compiled into the boot image to be used. It is an absolute (hex) debugger that allows breakpoints to be set, single-stepping through programs, displaying and editing memory, disassembling code, and examining I/O ports.
This debugger can be used for debugging interrupt handlers.
The dumper utility will save the postmortem state of a program to disk. It utility runs in the background, and provides its postmortem dump service for all processes. Whenever a program terminates abnormally, the current state of the program is written to disk.(This can be redirected over a network to another node).
Both of these utilities are documented in the QNX OS Utilities - A to M manual.
There is a good section on remote debugging using the Watcom 10.6 Debugger in Chapter 10 of the Watcom Debugger manual that covers debugging over serial, parallel, and ethernet connections.
See Also: dumper and Debugger32 in QNX OS Utilities - A to M |
|
