btop: [BUG] RISCV64 images built by Actions do not work

Read the README.md and search for similar issues before posting a bug report!

Any bug that can be solved by just reading the prerequisites section of the README will likely be ignored.

Describe the bug

Using the latest riscv64 release, normal installation leads to a Segmentation fault output when trying to run. However, after building the image natively on my own hardware, I was able to install and use that binary normally. I am running a Lichee RV on Debian Sid with kernel 5.14.0-rc4.

Binaries built by GitHub Actions also do not work.

I realize that my hardware isn’t exactly top priority, but I feel this may merely be something wrong with the cross-compile environment.

To Reproduce

Download, extract, install, and run btop-riscv64-linux-musl.tbz

Expected behavior

btop would run normally, or (as it does with my otherwise working self-built image) complain about a missing UTF-8 locale

Screenshots

image

Info (please complete the following information):

  • btop++ version: v1.2.0
  • Binary: btop-riscv64-linux-musl.tbz
  • (If compiled) Compiler and version: cc-11 g++-11
  • Architecture: riscv64
  • Platform: Linux
  • Kernel: 5.14.0-rc4-nezha

Additional context

contents of ~/.config/btop/btop.log File (and directory) not generated

(try running btop with --debug flag if btop.log is empty) Same behavior, no logs

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:

Thread 1 (process 3530 "btop"):
#0  0x0000003ff7f67a88 in ?? ()
#1  0x0000003ff7f2cb5e in ?? ()
#2  0x0000003ff7f229e6 in std::basic_ios<char, std::char_traits<char> >::_M_cache_locale(std::locale const&) ()
#3  0x0000003ff7f22cb0 in std::basic_ios<char, std::char_traits<char> >::init(std::basic_streambuf<char, std::char_traits<char> >*) ()
#4  0x0000003ff7ef1e0e in ?? ()
#5  0x0000003ff7e6ae24 in ?? ()
#6  0x0000003ff7e71a1e in ?? ()
#7  0x0000003ff7f6f4b0 in ?? ()

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 20 (7 by maintainers)

Most upvoted comments

Any help in figuring out what’s going on would be greatly appreciated.

I will try to reproduce it on my own hardware and write back.