when a application compiled without largefile support (ends up using open() instead of open64()),
tries to open a file >=2GiB, that fails with errno="file too large".

$ dd if=/dev/null of=LARGEFILE count=0 bs=1 seek=$((1024*1024*1024*2)) 
# this is a simple and FAST way to get (empty/sparse) large files without any disk I/O
$ bitcollider -p LARGEFILE 
Cannot find file/dir LARGEFILE. Skipping.
(note the misleading error message duh...)

after a quick google search and a compile with
make CC="gcc -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE"
(<http://ac-archive.sourceforge.net/largefile/> seems a nice resource)
i get:
$ dd if=/dev/null of=LARGEFILE count=0 bs=1 seek=$((1024*1024*1024*2))
$ bitcollider -p LARGEFILE 
bitprint=SHKQMQW5SMHJKQWDTU3PAULNIX2ODLYN

but then with somewhat larger (+1meg) files it crashes
at some point, i would suspect the hashes with internal
block-states (ed2k or ftuuhash) there, i'll look at that
a bit further when i get to it...
(but i'm not the one to fix the whole app, i'm afraid)