summaryrefslogtreecommitdiff
path: root/library
Commit message (Collapse)AuthorAgeFilesLines
* tests: Fix type for check_fatal_proc_unmountedCraig Small2022-12-061-1/+1
| | | | | | | | | | | While ps used the correct type for PIDS_VM_RSS the test did not. For some reason this only appeared to be an issue for s390x References: https://bugs.debian.org/1025495 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* library: adapted for absent 'core id' in /proc/cpuinfoJim Warner2022-10-251-10/+23
| | | | | | | | | | | | | A big oops on my part - with a big thanks to Dr. Fink. [ this version eliminates an extraneous startup call ] [ to the 'stat_cores_verify' function as superfluous ] Reference(s): https://www.freelists.org/post/procps/For-procpsng4001-No-core-id-in-eg-aarch65-or-ppc64le-proccpuinfo Prototyped by: Dr. Werner Fink <werner@suse.de> Signed-off-by: Jim Warner <james.warner@comcast.net>
* library: tweak support of p-core/e-core identificationJim Warner2022-10-041-4/+3
| | | | | | | | Wow, after this we'll eliminate one 'jmp' instruction! [ plus we can also save a single precious whitespace ] Signed-off-by: Jim Warner <james.warner@comcast.net>
* library: provided for cpu p-core/e-core identificationJim Warner2022-09-282-3/+188
| | | | | | | | | | | | | | With Intel's 12th generation Alder Lake processors now providing two distinct types of core, it would be nice if the library offered some sort of clue to core type. Well, with this patch it does. We'll have 2 additional enumerators. One deals with the cpu's core association and the other provides the type of that core (P or E). [ now, all we need is for some program to exploit it ] Signed-off-by: Jim Warner <james.warner@comcast.net>
* library: address an 'uninitialised value' VALGRIND bugJim Warner2022-09-123-5/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Thanks to valgrind and his --track-origins=yes option, the problem and solution was suggested as shown below. [ and it was created in that commit referenced below ] But, after attacking this problem by adding a memset() call in pids.c, a 2nd valgrind oops, also shown below, was encountered. The dynamically acquired 'cmd' again! [ might help to explain why changes appear excessive ] Reference(s): . 1st valgrind discovery ==11111== Conditional jump or move depends on uninitialised value(s) ==11111== at 0x13425D: stat2proc (readproc.c:582) ==11111== by 0x137436: look_up_our_self (readproc.c:1613) ==11111== by 0x132196: fatal_proc_unmounted (pids.c:1388) ==11111== by 0x11BA4D: before (top.c:3580) ==11111== by 0x127E10: main (top.c:7173) ==11111== Uninitialised value was created by a stack allocation ==11111== at 0x132165: fatal_proc_unmounted (pids.c:1381) . Jul, 2022 - fatal_proc_unmounted refactored commit 52bd019d8ca09ecfec34b5020eb7b8d612c315f8 . 2nd valgrind discovery ==22222== 16 bytes in 1 blocks are definitely lost ==22222== by 0x4A0E60E: strdup (strdup.c:42) ==22222== by 0x133D00: stat2proc (readproc.c:587) ==22222== by 0x136E67: look_up_our_self (readproc.c:1613) ==22222== by 0x131BC7: fatal_proc_unmounted (pids.c:1390) ==22222== by 0x11B7C6: before (top.c:3580) ==22222== by 0x127828: main (top.c:7173) Signed-off-by: Jim Warner <james.warner@comcast.net>
* misc: Update pc file to new library nameCraig Small2022-08-291-2/+2
|
* library: Rename to libproc2Craig Small2022-08-292-0/+0
| | | | | | | | | | The newlib library used to be called libproc-2 but the new name is preferred. References: https://www.freelists.org/post/procps/Next-for-newlib,3 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* build-sys: Relocate library to library/Craig Small2022-08-2941-0/+13581
All the dependent programs needed to have their includes moved too Signed-off-by: Craig Small <csmall@dropbear.xyz>