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