Faster IT
Faster IT
We typically set `Row_setPidColumnWidth(Platform_getMaxPid());` only in `Machine_init`. It does not make much sense to change the PID width every iteration as this would wiggle the screen contents right and left....
@a17sol: Sure, go for it. Just make it proper cross-platform, please. No AI-compiles-and-fire PRs.
Just a note: Almalinux 9 inherited the increased CPU baseline (x86_64-v2) from RHEL 9. Checking the processor capabilities e.g. with the awk scripts from https://unix.stackexchange.com/questions/631217/how-do-i-check-if-my-cpu-supports-x86-64-v2 seems like a good idea.
@BenBE he just ran `gdb`⏎. And that answers "no stack" on `bt full` when no executable is being debugged. As per above, it may well be a mismatch between the...
@Zomebodi: can you paste the results of `cat /proc/cpuinfo` for a VM from them where running `htop` gets you an immediate FP exception?
`x86-64-v2` should be fine on a ~Haswell CPU BUT https://www.intel.com/content/www/us/en/support/articles/000090280/processors/intel-xeon-processors.html. Let's see what CPU @Zomebodi has.
yes, but Ubuntu compiles its code (like Debian) for the `x86-64-v1` processor baseline
that would be a `x86-64-v4` CPU. Any idea what virtualization solution "Interserver" use?
@aestriplex, @corneliusroemer Can we have a better fix than reverting everything to the previous state of brokenness?
may be try `TERM=ansi77 htop -n 1` ?