blob: faa7b5e589b9bfa41cfa1fac8cba83a04bcb6de2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
---
name: Bug report
about: Create a report to help us improve
title: "[BUG]"
labels: bug
assignees: aristocratos
---
**Describe the bug**
[A clear and concise description of what the bug is.]
**To Reproduce**
[Steps to reproduce the behavior:]
**Expected behavior**
[A clear and concise description of what you expected to happen.]
**Screenshots**
[If applicable, add screenshots to help explain your problem.]
**Info (please complete the following information):**
- btop++ version: `btop -v`
- Binary: [self compiled or static binary from release]
- (If compiled) Compiler and version:
- Architecture: [x86_64, aarch64, etc.] `uname -m`
- Platform: [Linux, FreeBSD, OsX]
- (Linux) Kernel: `uname -r`
- (OSX/FreeBSD) Os release version:
- Terminal used:
- Font used:
**Additional context**
contents of `~/.config/btop/btop.log`
(try running btop with `--debug` flag if btop.log is empty)
**GDB Backtrace**
If btop++ is crashing at start the following steps could be helpful:
(Extra helpful if compiled with `make OPTFLAGS="-O0 -g"`)
1. run (linux): `gdb btop` (macos): `lldb btop`
2. `r` to run, wait for crash and press enter if prompted, CTRL+L to clear screen if needed.
3. (gdb): `thread apply all bt` (lldb): `bt all` to get backtrace for all threads
4. Copy and paste the backtrace here:
|
