I’m studying UNIX programming and was experimenting with read/write system calls.
I have a file with a pair of integer:
4 5
and I wrote this code to read the numbers:
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <sys/stat.h>
#include <fcntl.h>
typedef struct prova {
int first;
int second;
} prova_t;
int main(void) {
int fd;
prova_t origin;
prova_t result;
ssize_t bytes_read;
size_t nbytes;
fd = open("file.bin", O_WRONLY | O_CREAT);
origin.first = 24;
origin.second = 3;
write(fd, &origin, sizeof(prova_t));
close(fd);
fd = open("file.bin", O_RDONLY);
nbytes = sizeof(prova_t);
/* 1.BAD */
bytes_read = read(fd, &result, nbytes);
write(STDOUT_FILENO, &(result.first), sizeof(int));
write(STDOUT_FILENO, &(result.second), sizeof(int));
close(fd);
/* 2.GOOD */
nbytes = sizeof(int);
bytes_read = read(fd, &(result.first), nbytes);
write(STDOUT_FILENO, &(result.first), bytes_read);
bytes_read = read(fd, &(result.second), nbytes);
write(STDOUT_FILENO, &(result.second), bytes_read);
return 0;
}
In my first attempt I tried to read the whole struct from file and write its members to stdout. In this way, along with the numbers, I get some weird characters
4 5
E�^�
In my second attempt I read the numbers one by one and there were no problems in the output.
Is there any way to read and write the struct using the first method?
Edit: I updated the code to reflect suggestion from other users but still getting strange characters instead of numbers
First, let’s do a hex dump to see what is really stored in the file.
hexdump -C b.txtorod -t x2 -t c b.txtare two examples (od is for octal dump, more common, less pretty output in my opinion)That’s is what the file looks like if it was a created as an ASCII text file (such as using a text editor like vi). You can use
man asciito double check the hexadecimal values.Now if you had a binary file that only contains two 8-bit bytes, in the system’s native byte ordering (e.g. little-endian for x86, big endian for MIPS, PA-RISC, 680×0) then the hexdump would look like:
Here is the code to both create (open & write) a binary file, and read it back.
Now the data file contents look like:
Because the integers were specified as 32-bit integers (32-bits / 8 bits per byte = 4 bytes). I’m using a 64-bit system (little endian, x86), so I wanted to be explicit so the your results should match, assuming little-endian.