Open programminghoch10 opened 3 months ago
Going off of frame 17 in UserTable.c:35, the crash happens inside of getpwuid
, which calls getpwuid_r
which in turn follows up with a call into libnss.
A quick search found a similar issue in libc 2.34+, which can be seen here. Another instance of a similar issue can be seen here.
Can you check if the issue persists when compiling htop
without statically linking?
Dynamically linked works fine.
Systemd present? Cf. https://github.com/htop-dev/htop/issues/503#issuecomment-826007195
Systemd present?
Yes, systemd is present on host where the fault happend, but not in the container i built it in.
Only the host where you run it is relevant as htop
tries to use getpwuid
and that gets resolved via NSS and that fails with nss-systemd
present.
duplicate of #503
I built the statically linked binary inside a podman container and copied it to the host. Running it crashes immediately with
A signal 8 (Floating point exception) was received.
Compiled on commit
2503239d9fb453b5d67d3b33690c5a8e914bc58c
(currentmain
).Crash Output
GDB full stacktrace
htop.objdump
gdb stacktrace as text file