Role of the Debug Database in OCDI Debugging (Microprocessor SDK)
The debug database is a collection of records for all controls, signals, and breakpoints in the embedded application VI hierarchy. The debug database also contains C line number information for nodes on the block diagram. The build VI initializes the database before the first C file is compiled, usually in the setup stage of the build VI. The C parser inserts records in the debug database for all signals, controls, and breakpoints. The list parser maps the breakpoint line numbers into relative symbol offsets and updates all breakpoint records in the debug database. Finally, the map parser resolves all symbols and updates all database records so they contain absolute addresses of the embedded application. The database snapshot is then saved in the LVM file, which is located in the project build folder. The debug daemon automatically loads the LVM file every time you debug a built application. The debug database also contains additional index tables that improve the performance of the database so the debug daemon does not have to sequentially search object records. Index tables are not stored in the LVM file. Instead, the debug daemon re-indexes the database every time the LVM file is loaded.