htop-dev
htop static crash
Duplicate of #FATAL PROGRAM ERROR DETECTED
Please check at https://htop.dev/issues whether this issue has already been reported. If no similar issue has been reported before, please create a new issue with the following information:
- Your htop version: '3.5.0-dev-bbc5b15'
- Your OS and kernel version (uname -a) Linux master 3.10.0-1160.88.1.el7.x86_64 #1 SMP Tue Mar 7 15:41:52 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
- Your distribution and release (lsb_release -a) unknown, maybe centos
- Likely steps to reproduce (How did it happen?) just command htop
- Backtrace of the issue (see below)
Error information:
A signal 11 (Segmentation fault) was received.
Setting information:
htop_version=3.5.0-dev-bbc5b15;config_reader_min_version=3;fields=0 48 17 18 38 39 40 2 46 47 49 1;hide_kernel_threads=1;hide_userland_threads=0;hide_running_in_container=0;shadow_other_users=0;show_thread_names=0;show_program_path=1;highlight_base_name=0;highlight_deleted_exe=1;shadow_distribution_path_prefix=0;highlight_megabytes=1;highlight_threads=1;highlight_changes=0;highlight_changes_delay_secs=5;find_comm_in_cmdline=1;strip_exe_from_cmdline=1;show_merged_command=0;header_margin=1;screen_tabs=1;detailed_cpu_time=0;cpu_count_from_one=0;show_cpu_usage=1;show_cpu_frequency=0;show_cpu_temperature=0;degree_fahrenheit=0;show_cached_memory=1;update_process_names=0;account_guest_in_cpu_meter=0;color_scheme=0;enable_mouse=1;delay=15;hide_function_bar=0;header_layout=two_50_50;column_meters_0=LeftCPUs2 Memory Swap;column_meter_modes_0=1 1 1;column_meters_1=RightCPUs2 Tasks LoadAverage Uptime;column_meter_modes_1=1 2 2 2;tree_view=0;sort_key=1;tree_sort_key=0;sort_direction=1;tree_sort_direction=1;tree_view_always_by_pid=0;all_branches_collapsed=0;screen:Main=PID USER PRIORITY NICE M_VIRT M_RESIDENT M_SHARE STATE PERCENT_CPU PERCENT_MEM TIME Command;.sort_key=Command;.tree_sort_key=PID;.tree_view_always_by_pid=0;.tree_view=0;.sort_direction=1;.tree_sort_direction=1;.all_branches_collapsed=0;screen:I/O=PID USER IO_PRIORITY IO_RATE IO_READ_RATE IO_WRITE_RATE Command;.sort_key=IO_RATE;.tree_sort_key=PID;.tree_view_always_by_pid=0;.tree_view=0;.sort_direction=-1;.tree_sort_direction=1;.all_branches_collapsed=0;
Backtrace information:
[0x413ad5] [0x48c760] [0x5227d7] [0x521631] [0x51ea49] [0x520cff] [0x51ea49] [0x5210a2] [0x525cfa] [0x51ea49] [0x51eaf9] [0x52614e] [0x52f73f] [0x52fb65] [0x51e771] [0x4e134f] [0x4e1187] [0x442b0c] [0x41b119] [0x403ab3] [0x484688] [0x486850] [0x404a65]
To make the above information more practical to work with, please also provide a disassembly of your htop binary. This can usually be done by running the following command:
objdump -d -S -w which htop > ~/htop.objdump
Please include the generated file in your report. Running this program with debug symbols or inside a debugger may provide further insights.
Thank you for helping to improve htop!
Segmentation fault (core dumped)
Has your htop build be compiled with both --enable-static AND --enable-systemd? If so, this is a known issue with systemd.
Static builds need to be built without systemd support.
Has your htop build be compiled with both
--enable-staticAND--enable-systemd? If so, this is a known issue with systemd.Static builds need to be built without systemd support.
no, just use git action static build