| 5 | | The BOINC client software consists of two programs: the '''client''', |
| 6 | | which runs applications and does network communication, and the '''Manager''', |
| 7 | | which provides a graphical user interface (GUI) to the core client. |
| | 5 | To report a bug, email the [mlist:boinc_alpha boinc_alpha] email list |
| | 6 | or directly to [ProjectPeople David and Rom]. |
| | 7 | '''Note: when you post to boinc_alpha, attachments are stripped from your email; |
| | 8 | include text inline rather than as attachments. |
| | 9 | There's a 1 MB limit.''' |
| | 10 | Please include: |
| | 11 | * The context: what platform, what version of BOINC, anything else that might be relevant. |
| | 12 | * What sequence of actions caused the problem. |
| | 13 | * The exact nature of the problem. |
| | 14 | * The relevant parts of your message logs (see below). |
| 13 | | If the manager crashes, look for the file '''stderrgui.txt''' in the BOINC data directory. |
| 14 | | It should have information about where the crash occurred. |
| 15 | | Email [ProjectPeople David and Rom], describing the situation and attaching this file. |
| | 22 | The BOINC client software consists of two programs: |
| | 23 | * the '''client''', which runs applications and does network communication; |
| | 24 | * the '''manager''', which provides a graphical user interface (GUI) to the client. |
| 21 | | The best way to report client problems is to reproduce them using the |
| | 33 | If the client or manager crashes, information about |
| | 34 | the crash is written to a file in the BOINC data directory: |
| | 35 | '''stderrgui.txt''' for the manager, '''stderrdae.txt''' for the client. |
| | 36 | Email [ProjectPeople David and Rom], |
| | 37 | describing the situation and attaching the relevant file. |
| | 38 | |
| | 39 | == Work-fetch and task scheduling bugs == |
| | 40 | |
| | 41 | The most common client problems involve |
| | 42 | |
| | 43 | * '''work fetch''': deciding when to request tasks, |
| | 44 | what project to request from, and how much work to request. |
| | 45 | * '''task scheduling''': deciding what tasks to run at a given point. |
| | 46 | |
| | 47 | The best way to report these types problems is to reproduce them using the |
| 28 | | |
| 29 | | * Report it to [ProjectPeople David]; we may need to improve the emulator. |
| 30 | | * If the client is crashing, |
| 31 | | check for a file '''stderrgui.txt''' in the BOINC data directory. |
| 32 | | Email [ProjectPeople David and Rom], describing the situation and attaching this file. |
| 33 | | Usually if the Manager shows "not connect" it means the client has crashed. |
| 34 | | You can verify this as follows. |
| 35 | | Windows: run the Task Manager (ctrl-shift-esc) and check that there's not process named 'boinc.exe'. |
| 36 | | Mac/Linux: run {{{ps}}} and check that there's not process named 'boinc'. |
| 37 | | * For non-crashing problems, email the [mlist:boinc_alpha boinc_alpha] email list or directly to [ProjectPeople David and Rom]. |
| 38 | | '''Note: when you post to boinc_alpha, attachments are stripped from your email; include text inline rather than as attachments. |
| 39 | | There's a 1 MB limit.''' |
| 40 | | Your bug report should include: |
| 41 | | * The context: what platform, what version of BOINC, anything else that might be relevant. |
| 42 | | * What sequence of actions caused the problem. |
| 43 | | * The exact nature of the problem. |
| 44 | | * The relevant parts of your message logs (see below). '''If you don't include this information, we probably won't be able to fix the bug.'''. |
