Changes between Version 1 and Version 2 of DebugClientWin
- Timestamp:
- Apr 25, 2007, 12:36:07 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DebugClientWin
v1 v2 1 1 = Debugging the BOINC Windows client = 2 2 3 == Symbol Files == 4 Symbol files are used by various Windows debugging engines to match up memory addresses to symbol names. Symbol names are names of variables, functions, and subroutines that a developer has named a piece of code before the compilation process. 3 5 4 == Symbol Files == 5 Symbol files are used by various Windows debugging engines to match up memory addresses to symbol names. Symbol names are names of variables, functions, and subroutines that a developer has named a piece of code before the compilation process. 6 7 Symbol files for BOINC can be found here:[http://boinc.berkeley.edu/dl/ http://boinc.berkeley.edu/dl/] 6 Symbol files for BOINC can be found on [http://boinc.berkeley.edu/dl/ http://boinc.berkeley.edu/dl/] 8 7 9 8 The files generally start out like boinc_xxx_pdb.zip where the xxx is the version of BOINC you are running. … … 11 10 The uncompressed files should be stored in the same directory as BOINC. 12 11 12 == Crashes == 13 If either BOINC or the BOINC Manager crash, (they unexpectedly stop running or disappear), there should be some diagnostic information recorded in stderrdae.txt for BOINC and stderrgui.txt for the BOINC Manager. 13 14 14 == Crashes == 15 If either BOINC or the BOINC Manager crash, (they unexpectedly stop running or disappear), there should be some diagnostic information recorded in stderrdae.txt for BOINC and stderrgui.txt for the BOINC Manager. 16 17 The diagnostic information we are looking for is called a call stack which is described below. 18 15 The diagnostic information we are looking for is called a call stack which is described below. 19 16 20 17 == Call stacks == 21 18 Call stacks help us identify where the problem is by telling us which file and what line number in the source code the error occurred in. 22 19 23 20 Here is an example of a good call stack: 24 25 21 26 22 {{{ … … 32 28 1: c:\boincsrc\main\boinc\client\client_state.c(431) +0 bytes (CLIENT_STATE::do_something) 33 29 }}} 34 Here is an example of a bad call stack:35 30 31 Here is an example of a bad call stack: 36 32 37 33 {{{ … … 47 43 48 44 == Extracting call stacks == 49 If we need a call stack to help solve a problem that doesn't manifest itself as a crash you can still extract a call stack from a running program using some freeware tools Microsoft publishes called Debugging Tools for Windows.50 45 51 The Debugging Tools for Windows can be found here: [http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx Debugging Tools for Windows] 46 If we need a call stack to help solve a problem that doesn't manifest itself as a crash you can still extract a call stack from a running program using some freeware tools Microsoft publishes called Debugging Tools for Windows. 47 48 The Debugging Tools for Windows can be found on [http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx Debugging Tools for Windows] 52 49 53 50 Once these tools are installed on your machine and the symbol files are extracted to the BOINC installation directory you can run 'WinDBG.exe' and attach to the 'BOINC.exe' process through the file menu to begin your debugging session. Once 'WinDBG.exe' has attached itself to 'BOINC.exe' you can view the call stack by typing 'kb' in the command window and then hitting enter. … … 72 69 0012fff0 00000000 00431aca 00000000 78746341 kernel32!BaseProcessStart+0x23 73 70 }}} 74 Warning: You may need to add the BOINC directory to 'WinDBG.exe' symbol search path from the File menu in order to get a valid call stack.75 71 72 Warning: You may need to add the BOINC directory to 'WinDBG.exe' symbol search path from the File menu in order to get a valid call stack.
