Thanks for looking into this issue; however, I do think that the selected solution only works around the problem and that this issue is likely to pop up again. A larger page size has made this problem surface, but it is not the root cause (which likely involves stream book keeping).
Its possible that other architectures will see this problem. IA-64 isn't the only architecture with a larger default page size - I'm not sure if there are others that are above 16K by default, but there might be others. Such systems would also get bit by this bug when they begin running a recent kernel. Also, the PAGE_SIZE on ia64 is a compile time option - its possible to go up to 64K pages. The default debian kernel doesn't do this, but its a reasonable thing for customers to configure themselves. This workaround could be enhanced to detect the system page size at runtime (via sysconf) and dynamically allocate buffers that match. Or, an easier, possibly slower workaround might be to always force fread to use an 8K buffer (similar to how my instrumentation patch forces 16K buffers to trigger the issue on x86). -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
