Search:

so you added that loop directly after the call to tokenize? i tried running it by adding those two lines and still got the garbled data in the array on the second iteration.

ok, here are the three files (i tried to attach the makefile but i think the site won't allow it). let me know if this works.

around line 150, i have both the "actual" code (that passes in the...

I can do the same thing and everything works fine. This is crazy! In both cases, the array argument looks fine when I enter the function. But something else must be going on...can I send you the...

so you ran that fine on your machine? how could that be? i ran this code on both a linux vm, and then on os x, and got the same result for both. assuming the array argument looks fine coming into...

sorry...forgot to take that line out. that's a leftover char* from when i tried, on each iteration, to copy the contents of path[i] into a temporary string pointer. i thought that would prevent any...

I actually have one at the beginning of the function, but I removed it before posting for brevity :)
So yes, the paths array definitely looks okay at the beginning of the function.

I have the following function in a tiny C app. I basically take in an array of directory paths (the "paths" argument) and, for each path, iterate over each file in the directory and print the file...