-
Bug
-
Resolution: Obsolete
-
Normal
-
None
-
rhel-9.3.0
-
None
-
None
-
rhel-sst-pt-perf-debug
-
ssg_platform_tools
-
2
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
Unspecified
-
None
Description of problem:
During testing of PCP a possible glibc bug has been discovered. PCP is using valgrind for some tests. One of these tests failed with the following valgrind log:
> Conditional jump or move depends on uninitialised value(s)
> at 0x4040410: strcmp (strcmp.S:76)
> by 0x4017E1B: check_match (dl-lookup.c:88)
> by 0x4017E1B: do_lookup_x (dl-lookup.c:447)
> by 0x4BC707B: do_dlsym (in /usr/lib64/libc.so.6)
> by 0x4BC6B97: _dl_catch_exception (in /usr/lib64/libc.so.6)
> by 0x4BC6CA7: _dl_catch_error (in /usr/lib64/libc.so.6)
> by 0x4030D87: _rtld_catch_error (dl-error-skeleton.c:260)
> by 0x4BC7367: __libc_dlsym (in /usr/lib64/libc.so.6)
> by 0x4B9C09F: module_load (in /usr/lib64/libc.so.6)
> by 0x4B9C853: __nss_module_get_function (in /usr/lib64/libc.so.6)
> by 0x4B9934F: __nss_lookup (in /usr/lib64/libc.so.6)
> by 0x4B9AFB7: __nss_passwd_lookup2 (in /usr/lib64/libc.so.6)
> by 0x4B12F5B: getpwuid_r@@GLIBC_2.17 (in /usr/lib64/libc.so.6)
>
Version-Release number of selected component (if applicable):
RHEL compose: RHEL-9.3.0-20230726.0
glibc: glibc-2.34-72.el9
valgrind: valgrind-3.21.0-7.el9
pcp: pcp-6.0.5-2.el9
How reproducible:
Seen on aarch64 and ppc64le architectures only.
I do not know how to directly reproduce this.
This issue appeared during automated testing of PCP and I was not successful to reproduce it manually.
Steps to Reproduce:
1. Unknown
Actual results:
A valdrind reports an issue in glibc.
Expected results:
No valgrind issues are reported.
Additional info:
- external trackers