There could be something wrong with `scheme_get_long_long_val`, but it's surprising that it could go wrong in a machine-specific way. Does the error happen for you even in a very short program that tries to set the file position to 1122398240, or does it only happen in your full program?
I just did some debug printing. The problem is more complicated than I thought. I was misled by the "too large" diagnostics message and thought that the problem is just the number, but it is not, or at least not only the number. The error pops out not on the first or second positioning exceeding 1 GB. In fact, it happens on different moments in different runs. This time, for instance, it happened on position 1120708256. Interesntigly, moments ago the positioning on the same number, and also with different numbers, on the same file, several times, did not raise an error. Here is the tail of the sequence of positioning numbers on the same file that ended with the error: 1120708256 46696208 46696208 46696208 1120708256 46696208 46696208 46696208 1120708256 46696208 46696208 46696208 1120708256 ---> error (other files were also positioned alternately with this one; not sure if it is important). Despite the presence of numbers < 1 GB in the sequence, the error always happens on numbers greater than 1 GB I never had a problem with the same program on 64-bit Linux. I can do some more tests if you need them. I could use a hint about what kind of test would be useful to track down the problem. Best regards, Dmitry -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/5cddd0ee-9c39-600b-2f1b-0ae7b60db37c%40iaaras.ru.
