

mmap_P failures


I have same failures in the mmap_P test case of the binary RPM.
The problem is: Some of the mmap calls should fail. But the parameters
are calculated for the machine, where the RPM was build. On other
machines, the following happens: The program mmaped the area, where
the shared libraries are. Normally, this mmap should fail. But if
you have more memory/swap than the machine had where the test was
compiled on, it will not fail and you will overwrite your shared
libc with zeros.

Any ideas how to solve this?


SuSE Linux AG        Deutschherrenstr. 15-19       D-90429 Nuernberg

Reply to: