Hi,
We are seeing an issue with seek and ftell leaking memory with files larger than 2GB.
We are using 2.0.11 guile built as a 32-bit application with large file support enabled (guile was built using gcc 4.4.0 for Linux with flags _FILE_OFFSET_BITS=64, _LARGEFILE_SOURCE and _LARGEFILE64_SOURCE). The issue also appears to happen with guile 2.2.
The memory leaks start only after the offset exceeds maximum positive value for a 32-bit signed integer. ftell and seek do work as expected (given how lseek should work with large file support).
Appended is a program that illustrates the problem. The first seek simply skips the part of the file where you won't see a memory leak. If you comment out ftell and the second seek lines and un-comment the lines that follow them, there is no memory leak.
Is this a bug in guile or should we be doing things differently? If this is a known issue, is there a recommended work around?