summaryrefslogtreecommitdiffstats
path: root/.github/ISSUE_TEMPLATE/crash.md
diff options
context:
space:
mode:
Diffstat (limited to '.github/ISSUE_TEMPLATE/crash.md')
-rw-r--r--.github/ISSUE_TEMPLATE/crash.md33
1 files changed, 33 insertions, 0 deletions
diff --git a/.github/ISSUE_TEMPLATE/crash.md b/.github/ISSUE_TEMPLATE/crash.md
new file mode 100644
index 0000000..28d7bfe
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/crash.md
@@ -0,0 +1,33 @@
+---
+name: Crash report
+about: A hard crash of the interpreter, possibly with a core dump
+labels: "type-crash"
+---
+
+<!--
+ Use this template for hard crashes of the interpreter, segmentation faults, failed C-level assertions, and similar.
+ Do not submit this form if you encounter an exception being unexpectedly raised from a Python function.
+ Most of the time, these should be filed as bugs, rather than crashes.
+
+ The CPython interpreter is itself written in a different programming language, C.
+ For CPython, a "crash" is when Python itself fails, leading to a traceback in the C stack.
+-->
+
+**Crash report**
+
+Tell us what happened, ideally including a minimal, reproducible example (https://stackoverflow.com/help/minimal-reproducible-example).
+
+**Error messages**
+
+Enter any relevant error message caused by the crash, including a core dump if there is one.
+
+**Your environment**
+
+<!-- Include as many relevant details as possible about the environment you experienced the bug in -->
+
+- CPython versions tested on:
+- Operating system and architecture:
+
+<!--
+You can freely edit this text. Remove any lines you believe are unnecessary.
+-->