If you read the man pages for readdir you will see that the pointer returned is not guaranteed to be valid beyond the next call. It could be to a location in memory that gets reused, or to a location that is freed, or whatever the implementors feel like.

Essentially, since you are attempting to store the result of readdir into a location that you will use after that call, you are breaking the above rule. So, either use readdir_r or copy the results of the readdir into a "struct dirent" before making the next call (and hope there's no other thread in the application using readdir concurrent to yours....).

If you want to continue using "readdir", you'd change:

Code:

struct entry {
        struct stat st;
        struct dirent pde;
    };

Notice pde is no longer a "struct dirent *".

Then change this line "list.entries[c]->pde = pde;" to this "list.entries[c]->pde = *pde;".

If you want to use readdir_r then you'll need to restructure the while loop a little. I'll leave that to you, but if you know this isn't a multi-threaded program then IMO there's no reason to use readdir_r other than it's safer for the future if your code gets thrown into a multi-threaded environment. Since it's not that much harder to use, I suppose you could just do it right now...but I'll leave it to you to decide.