Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| See Also How To: Reassign a Bug |
| ### Next Steps Decide on a Bug Fix Strategy Reassign a Bug |
| Activity: Locate the Cause of a Bug
Developer
|  |  |  | Fix a Bug |  |
|  | Participating Roles Responsible: Developer
### Overview When a bug is reported, it is up to the developer to find the cause of the bug. The developer can employ a number of tactics and tools to find the root cause of the bug. The strategy to fix the bug often becomes more apparent while locating the cause. Use development tools such as logs, a debugger, analysis of the code, or print statements to pinpoint the cause and record the location assessment. # Entry Criteria Dependencies: The test configuration is the same one used when the bug was found. Up-to-date source code must be available. # Sub-Activities
1 | Isolate Functional Area | In searching for the offending area of code, eliminate areas in the code that do not involve the bug.
2 | Trace Involved Code Areas | Using debugging tools, sparingly mark the identified code area with tags that provide output visually to a debugger or log file.
3 | Analyze System with External Tools | Optional In addition to tracing code, use other tools in the environment to gauge the effects on the system when running certain identified areas.
4 | Pinpoint the Problem | Run the defect scenario as many times as necessary to pinpoint the lines of code causing the problem.
5 | Perform Code Analysis | If debugging the code is not possible due to untraceable quantities such as performance or resource problem, analyze the code line-by-line to identify the problem
# Exit Criteria
| There is enough information from the identified bug location to develop a fix.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |