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, its useful to include the following information, otherwise it won’t be helpful:
8 
9 * Operating system
10 * Telescope version (i.e. @PACKAGE_STRING@)
11 * how to reproduce the crash, if known
12 
13 In addition, the backtrace (i.e. the state of the program at the moment of the crash) contains invaluable data to unveil the source of the bug.  Obtaining a backtrace is usually simple, but unfortunately depends on your system.
14 
15 On most system, you should find a file named ‘telescope.core’ or ‘<number>.core’ or just ‘core’ in the directory where you launched telescope (probably your home).
16 
17 Your shell may be configured to disallow coredumps.  If
18 
19 > $ ulimit -c
20 
21 prints 0 then you’ll need to enable coredumps using
22 
23 > $ ulimits -c unlimited
24 
25 and try to reproduce the bug again.
26 
27 To open a core file you need to install ‘gdb’ (the GNU debugger) and type
28 
29 > $ gdb telescope path/to/core-file
30 
31 If you’re using a linux distro with systemd (Arch, Fedora, Debian, ...) you have to use coredumpctl to obtain a backtrace.  Please refer to the following page on the Arch wiki:
32 
33 > https://wiki.archlinux.org/title/Core_dump
34 
35 in particular the “Examining a core dump” section.
36 
37 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@.
38 
39 > (gdb) bt
40 > ...prints lots of useful information...
41 > (gdb)
42 
43 To quit gdb, just type ‘q’ and enter.
44 
45 Thanks!