1 # Oops
2 
3 It seems that Telescope crashed last time!  Please consider reporting this bug so it can be fixed.
4 
5 => mailto:@PACKAGE_BUGREPORT@	@PACKAGE_BUGREPORT@
6 
7 When reporting a bug, please include the following information, otherwise it won’t be very helpful:
8 
9 * Operating system
10 * Telescope version (i.e. @PACKAGE_STRING@)
11 * how to reproduce the crash, if known
12 
13 If possible, a backtrace (the state of the program when it crashed) should be included too, as it contains invaluable data to understand the source of the bug.  Obtaining a backtrace is usually simple, but the exact procedure depends on the operating system.
14 
15 On most system, after a crash a file named ‘telescope.core’ or ‘<number>.core’ or just ‘core’ should appear in the directory where Telescope was launched (probably your home).
16 
17 The shell may have to be configured to allow coredumps.  Running
18 
19 > $ ulimits -c unlimited
20 
21 should enable core dump for the current session on most shells.
22 
23 Once the core dump is located, a backtrace may be obtained with the aid of a debugger, like ‘gdb’ (the GNU debugger) or ‘lldb’ (the LLVM debugger):
24 
25 > $ gdb telescope path/to/core-file
26 
27 On a linux distro with systemd (Arch, Fedora, Debian, ...) ‘coredumpctl’ may be needed to launch the debugger.  Please refer to the following Arch wiki page:
28 
29 => https://wiki.archlinux.org/title/Core_dump
30 
31 in particular the “Examining a core dump” section.
32 
33 At this point you should be at the GDB prompt.  Just type ‘bt’, press enter and copy all the output in a mail to @PACKAGE_BUGREPORT@.
34 
35 > (gdb) bt
36 > ...lots of useful information...
37 > (gdb)
38 
39 To quit gdb, just type ‘q’ and enter.
40 
41 Thank you!