libarchive reads too many chars when extracting a file

Posted by ojreadmore on Stack Overflow See other posts from Stack Overflow or by ojreadmore
Published on 2010-05-21T14:58:09Z Indexed on 2010/05/21 15:01 UTC
Read the original article Hit count: 234

Filed under:

tar

I've written a C program to extract files from a tar archive using libarchive.

I'd like to extract a file from this archive and print it to standard output. But I get extra characters. It's garbage, but it's from another file (possibly adjacent to it in the archive.) I expect output to end at </html>.

Here is the code that reads this tar file.

libarchive 2.8.3 compiled on mac os X 10.6.3. gcc 4.2 x86_64

ls -l vendar-definition.html gives me 1921 for the file size. And so shows tar tfv 0000.tar | grep vendar-definition.html. So reports the C output that states the file size. To me this seems correct.

Two possibilities I can see for why my output is not as expected: 1. I've made a beginner's mistake or 2. multibyte characters in the archive files has something to do with it.

Related posts about malloc

Malloc corrupting already malloc'd memory in C

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm currently helping a friend debug a program of his, which includes linked lists. His list structure is pretty simple: typedef struct nodo{ int cantUnos; char* numBin; struct nodo* sig; }Nodo; We've got the following code snippet: void insNodo(Nodo** lista, char* auxBin, int auxCantUnos){ … >>> More
Multidimensional array with unequal second dimension size using malloc()

as seen on Stack Overflow - Search for 'Stack Overflow'
Hello, I am playing around with multidimensional array of unequal second dimension size. Lets assume that I need the following data structure: [&ptr0]-[0][1][2][3][4][5][6][7][8][9] [&ptr1]-[0][1][2] [&ptr2]-[0][1][2][3][4] int main() { int *a[3]; int *b; int i; a[0] = (int *)malloc(10… >>> More
Cannot understand how new or malloc does work with BYTE*

as seen on Stack Overflow - Search for 'Stack Overflow'
I trying to allocate memory for 10 bytes BYTE* tmp; tmp = new BYTE[10]; //or tmp = (BYTE*)malloc(10*sizeof(BYTE)); But after new or malloc operation length of *tmp more than 10 (i.e. '\0' char not in 10 position in tmp array) Why? >>> More
C Programming: malloc and free within a loop

as seen on Stack Overflow - Search for 'Stack Overflow'
Hi all, I just started out with C and have very little knowledge about performance issues with malloc() and free(). My question is as such: if I were to call malloc() followed by free() in a while-loop that loops for, say, 20 times, would it run slower compared to if I were to call free() outside… >>> More
Wrapping malloc - C

as seen on Stack Overflow - Search for 'Stack Overflow'
I am a beginner in C. While reading git's source code, I found this wrapper function around malloc. void *xmalloc(size_t size) { void *ret = malloc(size); if (!ret && !size) ret = malloc(1); if (!ret) { release_pack_memory(size, -1); ret = malloc(size); … >>> More

Developer IT

libarchive reads too many chars when extracting a file - Developer IT

libarchive reads too many chars when extracting a file

c

malloc

tar

Related posts about c

Related posts about malloc

Malloc corrupting already malloc'd memory in C

Multidimensional array with unequal second dimension size using malloc()

Cannot understand how new or malloc does work with BYTE*

C Programming: malloc and free within a loop

Wrapping malloc - C

Categories cloud