Show More
| @@ -54,6 +54,16 b" with the subject '{app_name} Crash Report'." | |||||
| 54 | If you want to do it now, the following command will work (under Unix): |
|
54 | If you want to do it now, the following command will work (under Unix): | |
| 55 | mail -s '{app_name} Crash Report' {contact_email} < {crash_report_fname} |
|
55 | mail -s '{app_name} Crash Report' {contact_email} < {crash_report_fname} | |
| 56 |
|
56 | |||
|
|
57 | In your email, please also include information about: | |||
|
|
58 | - The operating system under which the crash happened: Linux, macOS, Windows, | |||
|
|
59 | other, and which exact version (for example: Ubuntu 16.04.3, macOS 10.13.2, | |||
|
|
60 | Windows 10 Pro), and whether it is 32-bit or 64-bit; | |||
|
|
61 | - How {app_name} was installed: using pip or conda, from GitHub, as part of | |||
|
|
62 | a Docker container, or other, providing more detail if possible; | |||
|
|
63 | - How to reproduce the crash: what exact sequence of instructions can one | |||
|
|
64 | input to get the same crash? Ideally, find a minimal yet complete sequence | |||
|
|
65 | of instructions that yields the crash. | |||
|
|
66 | ||||
| 57 | To ensure accurate tracking of this issue, please file a report about it at: |
|
67 | To ensure accurate tracking of this issue, please file a report about it at: | |
| 58 | {bug_tracker} |
|
68 | {bug_tracker} | |
| 59 | """ |
|
69 | """ | |
General Comments 0
You need to be logged in to leave comments.
Login now