Quote:
Originally Posted by Jason.nix
I have two questions:
1- I meant the final program. Suppose you run a program that you don't have access to its source code, but it doesn't run and you want to find out why. What should be done in this case?
2- What tools and techniques does someone whose job is a debugger use?
|
1. Send a bug report to the developer.
2. When debugging most people use memory dumps, file record dumps, error messages, log messages, the source code, and written documentation that explains the function of the program, the type of input expected by the program, and the type of output produced. Usually the written documentation is found as comments in the source code. Other sources of useful information is a description by the user or system administrator as to what they were trying to do with the program and what the results were.
Then there are debuggers (software, not people). They can be very useful but you have to set up a special test run to use the debugger. In most cases a programmer can find the bug using the above information faster than they can set up a debugger run.