Question

Possible Duplicate:
C programming, why does this large array declaration produce a segmentation fault?

I am reading an image in c language but i am unable to do so as my program is stopping in between… after debugging i found that it is due to array size… is there any restriction on maximum size of array?
if i declare array of size 1400X1400 everything works fine but if i define array of size 1600X1400 my program stops working… why it is so… is there any limit imposed by compiler or OS on array size? and if so what is solution for this in c.

    unsigned char idata[1400][1400]; //working fine
    unsigned char idata[1600][1400]; //not working

Answer 1

I am guessing that idata is a local variable. The problem is that local variables are stored on the stack (technically “automatic storage”), and the stack is much smaller than the 6400 megabytes you’re trying to allocate on it. Allocating that much storage on it causes a stack overflow.

Try

unsigned char** idata = new unsigned char*[DIM1];

for (int i = 0; i < DIM1; ++i)
    idata[i] = new unsigned char[DIM2];

// or

unsigned char (*idata)[DIM2] = new char[DIM1][DIM2];

To allocate it in the free store and you shouldn’t have a problem.

EDIT:

I just looked at the tags and didn’t see you were only talking about C. If so, you can do the same thing but use malloc instead of new:

unsigned char** idata = malloc(sizeof(unsigned char*) * DIM1);

for (i = 0; i < DIM1; ++i)
    idata[i] = malloc(DIM2);

// or

unsigned char (*idata)[DIM2] = malloc(DIM1 * DIM2);

And don’t forget to free (or delete[] for C++) the memory you allocate to avoid memory leaks.