Arni

> Ok this took some time. Did you experience this with `-O2` as well? You said that you're going to try it with no optimizations at all. This would be...

> @Gerodote Hi, would you mind trying to build with as similar as possible flags with `gcc` and also try one of the `musl` binaries from https://github.com/aristocratos/btop/releases/tag/v1.2.13. > > If...

> The musl binary is static, it works on all 2.6+ kernels. ok, after testing nobounce's ebuild and after nobounce's ebuild with GCC .

nobounce's ebuild + clang no lto, no debug symbols, no native flags, maybe O2 :  ``` #0 0x00007ffff7f3d92b in std::__1::basic_streambuf::uflow() () from /usr/lib64/libc++.so.1 #1 0x00005555555cbec6 in ?? () #2...

IDK how, I got even another SIGSEGV with clang lto and nobounce's ebuild: ``` #0 0x00007ffff7f3b92b in ?? () #1 0x00007ffff75fe710 in ?? () #2 0x00005555555cbec6 in std::__1::basic_streambuf::sbumpc[abi:v160006]() (this=0x7ffff003b5a0) at...

I'll try get more packages with debug symbols.

 ``` #0 0x00007ffff7f3b96b in std::__1::basic_streambuf::uflow ( this=0x7ffff75fe720) at include/c++/v1/streambuf:447 #1 0x00007ffff7f3e1cf in std::__1::basic_streambuf::sbumpc ( this=0x7ffff002e110) at include/c++/v1/streambuf:191 #2 std::__1::basic_istream::ignore (this=0x7ffff75fe710, __n=9223372036854775807, __dlm=32) at include/c++/v1/istream:962 #3 0x00005555556ef5ec in Proc::collect (no_update=false)...

It seems to happen if -stdlib=libc++ .

tests leak too. ``` UpdateCTestConfiguration from :/home/paxu/data/code/experiments/fmtlog_cmake_fix/build/Clang_20.0.0gitfd7d7882_x86_64-pc-linux-gnu/Debug/DartConfiguration.tcl UpdateCTestConfiguration from :/home/paxu/data/code/experiments/fmtlog_cmake_fix/build/Clang_20.0.0gitfd7d7882_x86_64-pc-linux-gnu/Debug/DartConfiguration.tcl Test project /home/paxu/data/code/experiments/fmtlog_cmake_fix/build/Clang_20.0.0gitfd7d7882_x86_64-pc-linux-gnu/Debug Constructing a list of tests Done constructing a list of tests Updating test list for fixtures Added...

it fails with fmtlib 11.0.2 , 10.2.1 and 9.1.0 . It seems to be definitely fmtlog's problem.