Bad offset (option -s) can't count after 0xFFFFFFFF

[Emen0s]

Hello !

I use Strings2 evryday for work.
I think I have found an issue with the -s parameter on very large file.

I use strings2 -s on full RAW disk images.

I found that the offset can't count after 0xFFFFFFFF.
It just go to 0x00000001 after.
So every offset after 0xFFFFFFFF on my result is bad, so my tools won't work (I use the offset from strings2 to automatically carve for files).

Thank you very much for your work !
A fix would be very very pleased !

Have a nice day !

[Al3x101]

Hi, I thought I was going mad, things were failing part way through searches. It seems I have found the exact same issue with the file offset. Same issue in Strings (original version) also, so it looks like the fork carried the same bug over.