htop.txt

negge@canaan ~ $ htop


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.3.0'
  - Your OS and kernel version (uname -a)
  - Your distribution and release (lsb_release -a)
  - Likely steps to reproduce (How did it happen?)
  - Backtrace of the issue (see below)

Error information:
------------------
A signal 6 (Aborted) was received.

Setting information:
--------------------
htop_version=3.3.0;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;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=AllCPUs Memory Swap;column_meter_modes_0=1 1 1;column_meters_1=Tasks LoadAverage Uptime;column_meter_modes_1=2 2 2;tree_view=0;sort_key=46;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=PERCENT_CPU;.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:
----------------------
htop(+0x17448)[0x2add245448]
htop(CRT_handleSIGSEGV+0xba)[0x2add24568a]
linux-vdso.so.1(__vdso_rt_sigreturn+0x0)[0x3fce6a7800]
/usr/lib64/libc.so.6(+0x6cccc)[0x3fce4cbccc]
/usr/lib64/libc.so.6(gsignal+0x12)[0x3fce4963de]
/usr/lib64/libc.so.6(abort+0xac)[0x3fce4862d4]
htop(xMalloc+0x0)[0x2add2566ec]
htop(xSnprintf+0x56)[0x2add256c1e]
htop(Process_writeField+0x1c4)[0x2add24e6ae]
htop(+0x2b7fe)[0x2add2597fe]
htop(Row_display+0x2e)[0x2add24f4f4]
htop(Panel_draw+0x15e)[0x2add24c6a0]
htop(ScreenManager_run+0x114)[0x2add251592]
htop(CommandLine_run+0x5a2)[0x2add24437c]
/usr/lib64/libc.so.6(+0x27688)[0x3fce486688]
/usr/lib64/libc.so.6(__libc_start_main+0x74)[0x3fce486730]
htop(_start+0x20)[0x2add240994]

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!

Aborted