ddru_ntfsfindbad Does not show damaged files on 3Gb GPT partition

[KDEboroda]

ddru_ntfsfindbad Does not show damaged files on 3Gb GPT partition
It just creates an empty file.
While ddru_ntfsbitmap works fine.
$MFT contains just 7680 records and mapfile is 5,2 M long. What's the problem? Compilation issues? Incompatibility with >2Gb partitions? Anything else? I can show the logfile, if needed.
Here is the output of the program:
root@k-desktop:~/ddrutility-2.7/src# ./ddru_ntfsfindbad /dev/sda /home/k/log_toshiba_to_wd.txt -VVVV -i135266304
ddru_ntfsfindbad 1.5 20150109
Reading the logfile into memory...
processed 181650 lines out of 181658 with 0 errors
Reading partition boot sector...
Reading mft inode...
total mft fragments=2
total mft size=7864320 bytes
total inodes=7680
mftpart=0, offset=0xC8100000, fulloffset=0xD0200000, size=0x740000
mftpart=1, offset=0x2B2BD964000, fulloffset=0x2B2C5A64000, size=0x40000
processing inode 7680 of 7680
MFT hard errors=0
MFT soft errors=0
Skipped deleted inodes=0
ddru_ntfsfindbad took 14.487992 seconds to complete

[maximus57]

I believe the problem is not that the disk is too big, but that the files are likely large and fragmented enough that the data run information does not fit in the actual MFT record and is stored elsewhere on the drive. Unfortunately I did not accomodate for this when I wrote the program as file system information is hard to come by. At this time I do not plan on updating the ddrutility suite as I am working on a different project group, the most important is HDDSuperClone which is a new cloning tool meant to replace ddrescue. It is very muich functional as a cloning tool but is still a work in progress, and in time I am planning on adding extra functions such as processing the bitmap and mft directly in the cloning tool. Until then I am sorry that ddru_ntfsfindbad does not seem to work in all cases.