Hide Forgot
*** Bug 1520995 has been marked as a duplicate of this bug. ***
------- Comment From shriykul.com 2018-02-12 03:42 EDT------- Verified on Pegas 1.1 Snap 2: =================== uname -r : 4.14.0-39.el7a.ppc64le Machine : Boston + DD2.2 Testing : ====== [root@ltc-boston122 ~]# readelf -n /lib64/libc.so.6 | grep memory_mallopt_mmap_threshold -A2 -B2 stapsdt 0x00000051 NT_STAPSDT (SystemTap probe descriptors) Provider: libc Name: memory_mallopt_mmap_threshold Location: 0x000000000009bbf0, Base: 0x00000000001a1010, Semaphore: 0x0000000000000000 Arguments: -4@30 8@0(9) -4@0(10) [root@ltc-boston122 ~]# readelf -n /lib64/libc.so.6 | grep memory_mallopt_mmap_max -A2 -B2 stapsdt 0x0000004b NT_STAPSDT (SystemTap probe descriptors) Provider: libc Name: memory_mallopt_mmap_max Location: 0x000000000009bcc0, Base: 0x00000000001a1010, Semaphore: 0x0000000000000000 Arguments: -4@30 -4@0(7) -4@0(8) Able to see the enteries in the format : N@OP where N maybe any one of -1, -2, -4, -8, 1, 2, 4, 8 OP maybe in any one of the following formats iNUM or i-NUM REG or %rREG NUM(REG) or -NUM(REG) or NUM(%rREG) or -NUM(%rREG) REG,REG or %rREG,%rREG where NUM is any numeric constant and REG is a register index (0 to 31). [root@ltc-boston122 ~]# readelf -n /lib64/libc-2.17.so | grep "Arguments: " Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@28 -4@i1 -4@i0 Arguments: 8@27 -4@i1 -4@i0 Arguments: 8@23 -4@i1 -4@i0 Arguments: 8@23 -4@i1 -4@i0 Arguments: 8@23 -4@i1 -4@i0 Arguments: 8@23 -4@i1 -4@i0 Arguments: 8@29 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@25 -4@i1 -4@i0 Arguments: 8@25 -4@i1 -4@i0 Arguments: 8@25 -4@i1 -4@i0 Arguments: 8@27 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0 Arguments: 8@31 -4@i1 -4@i0
Finished testing systemtap-3.2-4.el7.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0906