* Kevin Kofler via devel:
Florian Weimer wrote:
> It's not. It may be a completely different system call.
So now I had a new idea how to figure out what difference the version of
glibc we are compiling against can make: track down the symbol version:
nm -D --with-symbol-versions Downloads/libQt5WebEngineCore.so.5.15.2 | grep
'(a)GLIBC_2\.33'
U fstat64(a)GLIBC_2.33
U fstatat64(a)GLIBC_2.33
U lstat64(a)GLIBC_2.33
U stat64(a)GLIBC_2.33
So we are getting new symbol versions of the above 4 functions. So now we
only need to know what is different between the above and the syscalls
presumably used previously:
nm -D --with-symbol-versions Downloads/libQt5WebEngineCore.so.5.15.1 | grep
'stat\(at\)\?64'
U __fxstat64(a)GLIBC_2.2.5
U __fxstatat64(a)GLIBC_2.4
U __lxstat64(a)GLIBC_2.2.5
U __xstat64(a)GLIBC_2.2.5
(That's the version from F33 GA, definitely built against an older glibc.)
Right, and the glibc 2.33 versions all call fstatat64 in the end (system
call number 0x106). The older x versions call the earlier system calls
(numbers 4, 5, 6).
Thanks,
Florian
--
Red Hat GmbH,
https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill