Valgrind: Invalid read of size 1

Question

I'm having an issue with valgrind: This is my program (well the main part where the errors appear):

int main()
{
char comanda[N];
....
char *p;
while( fgets(comanda,100,stdin)!=NULL)
    {
    p=strtok(comanda," \n");
    if (strcmp(comanda,"INIT")==0)
        {
        p=strtok(NULL," ");
        Init(n);        
        }
395 >>if (strcmp(p,"DUMP")==0)
        {
        Dump(n);}
    if (strcmp(p,"ALLOC")==0)
        {
        Alloc(j,n);
        }
    ....return 0;}

And when i run valgrind it says:

Invalid read of size 1
at 0x401569: main (:395)
Address 0x0 is not stack'd malloc'd or (recently) free'd

I can't figure out what's the matter with this program.

It also might be a good idea to run programs under a debugger to determine what they're doing wrong. — Michael Burr, Dec 28 '12 at 09:39
No need for a debugger here, valgrind exactly says what is going on here. @user1934103, please read what it is telling you. What address could be `0x0` at the place it is indicating? So it is telling you that `p` is `0`. — Jens Gustedt, Dec 28 '12 at 10:27

score 33 · Answer 1 · answered Dec 28 '12 at 09:58

How to read this:

Invalid read of size 1

Your program is trying to read one byte from somewhere that Valgrind doesn't like.

at 0x401569: main (:395)

Where in the code this happens (clearly strcmp has been inlined)

Address 0x0 is not stack'd malloc'd or (recently) free'd

What the address it was reading - 0x0 is "NULL". The rest of the statement just says why it's invalid (it's not from the stack, it's not something you've got from malloc, and not been freed recently). The "recently" is mentioned because valgrind keeps track of freed memory for a limited number of frees, so it can't say for sure that it wasn't freed a million frees back - in this case it wasn't, but if you see a message like that, it MAY be that it has become invalid because it was freed ages ago. The address would not be zero tho' (or near zero).

score 8 · Answer 2 · answered Dec 28 '12 at 09:38

8

It is possible for strtok to return NULL when there are no more tokens left.

When you pass NULL to strcmp it is an undefined behavior as you de-reference NULL there.

answered Dec 28 '12 at 09:38

codaddict

445,704
82
492
529

Valgrind: Invalid read of size 1

2 Answers2

Linked