| Abstrakt: |
Errors in code are inevitable. The occurrence of errors is manifested as standard exceptions, as hangs where the central processing unit is being used 100 percent of the time, as deadlocks, where a couple of threads are locked and will never release the other's resources. In these cases, error logs often provide little or no help in pin-pointing the exact line of code in which the problem originates. As users cannot usually isolate the root cause by modifying code in a production environment on workstations. They copy the specific components, the customer's data base and then try to reproduce the problem in their debugger. This article demonstrates how to solve each of the problems described using managed and unmanaged applications without having to recreate the production environment. It also shows how to find the root cause using the appropriate debugger commands. |
