htop Linux signal tables for Alpha, SPARC, MIPS & PARISC

Aug 29 '16 12:08 Explorer09

Hi, did you stumble upon any of these machines?

Aug 30 '16 15:08 hishamhm

@hishamhm No, I don't have any of them (the machines). What I cared is that the Linux signal man page already stated that some architectures have different signal numbers, and I would consider that a bug if we don't support it or at least detect it at configure time.

Note that many kill utilities (from bash, procps, or busybox) don't have this signal table problem because they grab the signal numbers from the system headers (at compile time), which glibc has already taken care of (see sysdeps/unix/sysv/linux/<arch>/bits/signum.h in its source code). Htop uses hard-coded tables instead of fetching numbers from libc, so we should include tables for all architectures.

Aug 30 '16 15:08 Explorer09

htop started to crash on my samsung note 8.

--------- beginning of crash 02-03 04:20:22.748 16527 16527 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 16527 (htop) 02-03 04:20:22.819 16530 16530 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 02-03 04:20:22.819 16530 16530 F DEBUG : Build fingerprint: 'samsung/greatqltecs/greatqltecs:8.0.0/R16NW/N950WVLU5CRJ3:user/release-keys' 02-03 04:20:22.819 16530 16530 F DEBUG : Revision: '11' 02-03 04:20:22.819 16530 16530 F DEBUG : ABI: 'arm64' 02-03 04:20:22.819 16530 16530 F DEBUG : pid: 16527, tid: 16527, name: htop >>> htop <<< 02-03 04:20:22.819 16530 16530 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- 02-03 04:20:22.819 16530 16530 F DEBUG : x0 0000000000000000 x1 000000000000408f x2 0000000000000006 x3 0000000000000008 02-03 04:20:22.819 16530 16530 F DEBUG : x4 fefeff6b2f2f2f30 x5 fefeff6b2f2f2f30 x6 fefeff6b2f2f2f30 x7 0000000000000040 02-03 04:20:22.819 16530 16530 F DEBUG : x8 0000000000000083 x9 8cf1c4a827bc51e3 x10 0000000000000000 x11 0000000000000001 02-03 04:20:22.819 16530 16530 F DEBUG : x12 ffffffffffffffff x13 0000007fdd412980 x14 0000007587303334 x15 0000000000000000 02-03 04:20:22.819 16530 16530 F DEBUG : x16 00000075873212f8 x17 00000075872c2810 x18 0000000000002710 x19 000000000000408f 02-03 04:20:22.819 16530 16530 F DEBUG : x20 000000000000408f x21 0000000000000021 x22 0000007586e39320 x23 0000000000000021 02-03 04:20:22.820 16530 16530 F DEBUG : x24 0000000000000001 x25 0000000000000001 x26 0000000000000023 x27 0000000000000003 02-03 04:20:22.820 16530 16530 F DEBUG : x28 0000007586e30960 x29 0000007fdd4129a0 x30 0000007587274f14 02-03 04:20:22.820 16530 16530 F DEBUG : sp 0000007fdd412960 pc 00000075872c2818 pstate 0000000060000000 02-03 04:20:22.821 16530 16530 F DEBUG : 02-03 04:20:22.821 16530 16530 F DEBUG : backtrace: 02-03 04:20:22.822 16530 16530 F DEBUG : #00 pc 000000000006b818 /system/lib64/libc.so (tgkill+8) 02-03 04:20:22.822 16530 16530 F DEBUG : #01 pc 000000000001df10 /system/lib64/libc.so (abort+88) 02-03 04:20:22.822 16530 16530 F DEBUG : #02 pc 000000000001b540 /data/data/com.termux/files/usr/bin/htop 02-03 04:20:22.832 16530 16530 I crash_dump64: Start bugreportnat 02-03 04:20:22.844 1491 2485 W NativeCrashListener: Couldn't find ProcessRecord for pid 16527 02-03 04:20:22.846 1074 1074 W /system/bin/tombstoned: crash socket received short read of length 0 (expected 8) 02-03 04:20:22.859 1491 1561 I BootReceiver: Copying /data/tombstones/tombstone_03 to DropBox (SYSTEM_TOMBSTONE) 02-03 04:20:22.871 16532 16532 E propClient: PropClient failed to load 02-03 04:20:22.885 16532 16532 E propClient: PropClient failed to load 02-03 04:20:22.889 1491 1557 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver 02-03 04:20:22.889 3578 3578 D ContextFramework: ContextBroadcastReceiver : received DropBoxManager "SYSTEM_TOMBSTONE" event 02-03 04:20:22.892 1491 1557 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver 02-03 04:20:22.945 16531 16531 E propClient: PropClient failed to load 02-03 04:20:22.948 16531 16531 D dumpstate: Loading stats from /data/log/dumpstate-stats.txt 02-03 04:20:22.949 16531 16531 E dumpstate: Invalid stats line on file /data/log/dumpstate-stats.txt: 1010 1528 02-03 04:20:22.949 16531 16531 I dumpstate: Average max progress: 1528 in 1010 runs; estimated max: 5000 02-03 04:20:22.950 16531 16531 I dumpstate: begin 02-03 04:20:22.950 16531 16531 I dumpstate: dumpstate info: id=1587, args='/system/bin/dumpstate', extra_options= bugreportnat) 02-03 04:20:22.950 16531 16531 I dumpstate: bugreport format version: 1.0 02-03 04:20:22.951 16531 16531 D dumpstate: Bugreport dir: /data/log 02-03 04:20:22.951 16531 16531 D dumpstate: Base name: dumpstate_app_native 02-03 04:20:22.951 16531 16531 D dumpstate: Suffix: undated 02-03 04:20:22.951 16531 16531 D dumpstate: Log path: /data/log/dumpstate_app_native-undated-dumpstate_log-16531.txt 02-03 04:20:22.951 16531 16531 D dumpstate: Temporary path: /data/log/dumpstate_app_native-undated.tmp 02-03 04:20:22.951 16531 16531 D dumpstate: Screenshot path: 02-03 04:20:22.951 16531 16531 D dumpstate: Creating initial .zip file (/data/log/dumpstate_app_native.zip) 02-03 04:20:22.951 16531 16531 D dumpstate: Adding zip text entry version.txt 02-03 04:20:22.956 1491 2120 I WifiTrafficPoller: mCpuCoreBooster Lock 02-03 04:20:22.956 1491 2120 I SemDvfsCpuCoreManager: acquire:: timeout = 2000, mIsAcquired = true , mTagName : WIFI_TP@4 02-03 04:20:22.983 16537 16537 E propClient: PropClient failed to load 02-03 04:20:22.992 712 712 E SLPI_FACTORYD: left = 32 02-03 04:20:22.992 712 712 I SLPI_FACTORYD: process_message: 27 02-03 04:20:22.993 712 712 I SLPI_FACTORYD: main: do while start = 32 02-03 04:20:22.994 712 2921 I SLPI_FACTORYD: STATE: Type- 0 06a 0 0 10 0 02-03 04:20:22.994 712 2921 I SLPI_FACTORYD: STATE: Type- 10 0 0 0 0 10 0 02-03 04:20:22.994 712 2921 I SLPI_FACTORYD: STATE: Type- 20 0 9 0 0 10 0 02-03 04:20:22.994 712 2921 I SLPI_FACTORYD: STATE: Type- 30 0b1 0 0 10 0 02-03 04:20:22.994 712 2921 I SLPI_FACTORYD: STATE: Type- 40 0ec 0 0 0 0 02-03 04:20:22.994 712 2921 I SLPI_FACTORYD: STATE: Type-240 0 0 0 0 0 0 02-03 04:20:22.994 712 2921 I SLPI_FACTORYD: STATE: Type-243 0 0 0 0 0 0 02-03 04:20:23.038 16531 16531 E dumpstate: can't find the pid 02-03 04:20:23.038 16531 16531 E dumpstate: Failed to find: /data/misc/anrd/ 02-03 04:20:23.040 16531 16531 D dumpstate: Adding dir /cache/recovery (recursive: 1)

Feb 03 '19 09:02 diehard88