https://bugs.kde.org/show_bug.cgi?id=514206
--- Comment #2 from Brayton Hackbarth <[email protected]> --- Hello Paul, thanks for responding so quickly. Yes, I observed identical behavior on 3.26. Reproducing this elsewhere might pose a challenge because I'm not sure if this is hardware-specific (but I can say that even with identical hardware, I don't get the assert on Centos 6 or 7). Rocky9 is happy to let me read the file "resource" via in the PCI device directory, but not resource0, 1, etc. It will always throw a "Input/output error" or errno 5, almost as if there is a policy preventing standard I/O. However, it is quite happy to allow opening a file descriptor to the file. The hardware is a PTP hardware clock that is being disciplined based on a PPS input, so it's not exactly cheap and plentiful to obtain for testing. I was hoping that perhaps there could be a flag set in Valgrind to differentiate between mmap() ing physical devices versus shared libs since kernel permissions seem to come into play with physical devices. -- You are receiving this mail because: You are watching all bug changes.
