Debug your module

Debugging a C or C++ module consists of the following general steps:
  1. Install the module on the database server.
  2. Set breakpoints in your source code file.
  3. Start and attach the debugger to the database server process.
  4. Register the module in your test database.
  5. Run SQL queries (unit tests) to test the source code marked with breakpoints.

Debug your module in Windows™

If you are debugging C or C++ module source code on Windows™, you use Microsoft™ Visual C++, the DBDK Visual C++ Add-In, and the IfxQuery tool. The Debug DataBlade Module command of the add-in installs the module on the local database server, starts the debugger and database server, and calls IfxQuery to register the module and run the unit tests that halt at breakpoints in the source code. The Debug DataBlade Module command functions only if the database server is installed on the same computer on which you are debugging.

Debug your module in UNIX™

If you are debugging a module on UNIX™, you must install the module, start the database server and debugger, register the module with BladeManager, and use DB-Access to execute SQL statements that halt at breakpoints in the source code.

Debug your module in Java™

Debugging a module written in Java™ consists of the following general steps:
  1. Install the module.
  2. Start the database server process.
  3. Register the module in your test database.
  4. Run SQL queries (unit tests) to test the source code marked with breakpoints.
  5. Examine the Java™ log file for errors.