Is there a way of knowing what error occurred when an ifstream seekg failed?
Printable View
Is there a way of knowing what error occurred when an ifstream seekg failed?
nm that, seekg doesn't seem to be able to handle files over 2G, is there any way around this?
I have read a bit about that, not much though it did just kinda pop up in an article. If I remeber the solution had something to do with splitting up the file into 2GB slices, or something like that.
I have solved it temporarily by using windows api's instead with SetFilePointerEx, but its kind of annoying. What do you mean split up the file in 2GB slices? into new files or just splitting the area where you read?
You could also try finding an I/O stream that uses a 64-bit streamoff type. After all, just because the MS implementation is stupid enough to use 32-bit types doesn't mean others are, too.