ftell at a position past 2GB

by

on long int

long int is supposed to be AT LEAST 32-bits, but C99 standard does NOT limit it to 32-bit.
C99 standard does provide convenience types like int16_t & int32_t etc that map to correct bit sizes for a target platform.

on ftell/fseek

ftell() and fseek() are limited to 32 bits (including sign bit) on the vast majority of 32-bit architecture systems. So when there is large file support you run into this 2GB issue.

POSIX.1-2001 and SysV functions for fseek and ftell are fseeko and ftello because they use off_t as the parameter for the offset.

you do need to define compile with -D_FILE_OFFSET_BITS=64 or define it somewhere before including stdio.h to ensure that off_t is 64-bits.

Read about this at the cert.org secure coding guide.

On confusion about ftell and size of long int

C99 says long int must be at least 32-bits it does NOT say that it cannot be bigger

try the following on x86_64 architecture:

#include <stdio.h>

int main(int argc, char *argv[]) {
    FILE *fp;
    fp = fopen( "test.out", "w");
    if ( !fp ) 
        return -1;
    fseek(fp, (1L << 34), SEEK_SET);
    fprintf(fp, "\nhello world\n");
    fclose(fp);
    return 0;
}

Notice that 1L is just a long, this will produce a file that’s 17GB and sticks a "\nhello world\n" to the end of it. Which you can verify is there by trivially using tail -n1 test.out or explicitly using:

dd if=test.out skip=$((1 << 25))

Note that dd typically uses block size of (1 << 9) so 34 - 9 = 25 will dump out '\nhello world\n'

More Related Contents:

  1. Why is the fgets function deprecated?
  2. Unable to open a file with fopen()
  3. Tried and true simple file copying code in C?
  4. Printf width specifier to maintain precision of floating-point value
  5. Read/write files within a Linux kernel module
  6. Is type-punning through a union unspecified in C99, and has it become specified in C11?
  7. Is it possible to iterate over arguments in variadic macros?
  8. Code for printf function in C [duplicate]
  9. Reading a line using scanf() not good?
  10. What does dot (.) mean in a struct initializer?
  11. C write in the middle of a binary file without overwriting any existing content
  12. What is the use of the `inline` keyword in C?
  13. C99 boolean data type?
  14. What is the correct type for array indexes in C?
  15. Flexible array member in C-structure
  16. How can you flush a write using a file descriptor?
  17. C equivalent to fstream’s peek
  18. Can I omit return from main in C? [duplicate]
  19. C variable declarations after function heading in definition [duplicate]
  20. state machines tutorials [closed]
  21. Does the C standard consider that there are one or two ‘struct uperms_entry’ types in this header?
  22. How to properly add hex escapes into a string-literal?
  23. Is there any reason not to use fixed width integer types (e.g. uint8_t)?
  24. How to tell GCC that a pointer argument is always double-word-aligned?
  25. Why does this code print two times? [duplicate]
  26. How can one flush input stream in C?
  27. Reading a file character by character in C
  28. How do I insert and delete some characters in the middle of a file?
  29. Declaring an array of negative length
  30. Why are compound literals in C modifiable

Leave a Comment