What is the best way to debug a custom ODBC driver on Windows? A former member of our team wrote the driver so we have the source available.
How do you attach a debugger to the driver? Or is it easier to just add ‘trace prints’ to the driver to see what is going on?
Related Questions
No related questions found
The best solution i found so far is a combination of trace prints and breakpoints (int 3) compiled into the driver.
Trace prints for general debug information and the breakpoints for pieces of the code where I need to more thoroughly investigate the inner state of the driver.