Changes between Version 13 and Version 14 of ReportBugs
- Timestamp:
- Apr 19, 2011, 11:10:33 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReportBugs
v13 v14 1 1 = Reporting 'hard' bugs = 2 2 3 If a bug can be easily reproduced, it's easy for us to fix. 'Hard' bugs are those that happen rarely or only on specific machines. The following information tells BOINC Alpha Testers (and anyone else who wants to help) how to report hard bugs, so that we can fix them even if we can't reproduce them. 3 If a bug can be easily reproduced, it's easy for us to fix. 4 'Hard' bugs are those that happen rarely or only on specific machines. 5 The following information tells BOINC Alpha Testers (and anyone else who wants to help) how to report hard bugs, 6 so that we can fix them even if we can't reproduce them. 4 7 5 8 == Background == 6 9 7 The BOINC client software consists of two programs: the '''core client''', which runs applications and does network communication, and the '''Manager''', which provides a graphical user interface (GUI) to the core client. It's possible to run the core client without a GUI. Each program produces two files in your BOINC directory: one for messages, one for crash reports. These files are named as follows: 10 The BOINC client software consists of two programs: the '''core client''', 11 which runs applications and does network communication, and the '''Manager''', 12 which provides a graphical user interface (GUI) to the core client. 13 It's possible to run the core client without a GUI. Each program produces two files in your BOINC directory: 14 one for messages, one for crash reports. 15 These files are named as follows: 8 16 9 17 * core client … … 17 25 18 26 == Reporting hard bugs == 19 Report hard bugs by email, either to the [mlist:boinc_alpha boinc_alpha] email list or directly to [ProjectPeople David and Rom]. '''Note: when you post to boinc_alpha, attachments are stripped from your email; include text inline rather than as attachments. There's a 200KB limit.''' Your bug report should include: 27 Report hard bugs by email, either to the [mlist:boinc_alpha boinc_alpha] email list or directly to [ProjectPeople David and Rom]. 28 '''Note: when you post to boinc_alpha, attachments are stripped from your email; include text inline rather than as attachments. 29 There's a 1 MB limit.''' 30 Your bug report should include: 31 20 32 * The context: what platform, what version of BOINC, anything else that might be relevant. 21 33 * What sequence of actions caused the problem. … … 24 36 25 37 In general we're only interested in bug reports for the current public release, or for the latest testing release. 38 26 39 == Crashes == 27 If the Manager suddenly goes blank and says 'not connected', it's almost certainly because the core client has crashed. You can verify this by 40 If the Manager suddenly goes blank and says 'not connected', it's almost certainly because the core client has crashed. 41 You can verify this by 28 42 '''Windows''':: 29 43 Run the Windows Task Manager (ctrl-shift-esc) and check that there's no process named 'boinc.exe'. … … 31 45 Run {{{ps}}} and check that there's no process named 'boinc'. 32 46 33 Each crash appends an entry to the crash-report file (stderrdae.txt for the core client). Here's [//stderrdae.txt an example of such an entry]. It has a long list of DLLs in use at the time of the crash, followed by several 'stack traces' showing where the various threads were executing. 47 Each crash appends an entry to the crash-report file (stderrdae.txt for the core client). 48 Here's [//stderrdae.txt an example of such an entry]. 49 It has a long list of DLLs in use at the time of the crash, 50 followed by several 'stack traces' showing where the various threads were executing. 34 51 35 Your bug report email should include the most recent entry from your crash-report file. Please edit the file to remove old entries, so that we don't get confused by them. 52 Your bug report email should include the most recent entry from your crash-report file. 53 Please edit the file to remove old entries, so that we don't get confused by them. 36 54 37 55 38 56 == Incorrect behavior == 39 If BOINC behaves incorrectly, we usually need the core client's message log to figure out what's going on. The message log describes what the core client is doing. It's identical to what's shown in the Messages tab of the Manager. By default the core client writes only a few messages. More detailed messages are enabled by turning on [ClientMessages logging flags]. This is done by editing the file `cc_config.xml` in your BOINC directory. For example, the following turns on the `task_debug` and `cpu_sched` flags (1 turns a flag on; 0 or unspecified turns it off): 57 If BOINC behaves incorrectly, we usually need the core client's message log to figure out what's going on. 58 The message log describes what the core client is doing. 59 It's identical to what's shown in the Messages tab of the Manager. 60 By default the core client writes only a few messages. More detailed messages are enabled by turning on [ClientMessages logging flags]. 61 This is done by editing the file `cc_config.xml` in your BOINC directory. 62 For example, the following turns on the `task_debug` and `cpu_sched` flags (1 turns a flag on; 0 or unspecified turns it off): 40 63 {{{ 41 64 <cc_config> … … 61 84 (in both cases, it's better to err on the side of including too much). 62 85 63 Some common problem types, and the suggested logging flags, are listed below. You should also check the [ClientMessages complete list of logging flags]. 86 Some common problem types, and the suggested logging flags, are listed below. 87 You should also check the [ClientMessages complete list of logging flags]. 64 88 65 89 === BOINC gets too much or too little work ===
