Is there any limitation on the maximum size of array in c?

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

I think the compiler and device are the most likely sources of limitation, I have never encountered a limit like this in C language. We most likely really need to see the code where it is failing -- unless it isn't compiling at all. — Alan Moore, Sep 23 '12 at 14:05
The type `size_t` is used to specify the maximum object size in bytes (where byte = `char`) in standard C (1999 standard). The maximum value of `size_t` is `SIZE_MAX` (defined in ``). — Alexey Frunze, Sep 24 '12 at 06:16

Seth Carnegie · Accepted Answer · 2012-09-23T14:17:00.517

8

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.

edited Sep 23 '12 at 14:17

answered Sep 23 '12 at 14:04

Seth Carnegie

73,875
22
181
249

@Flexo usually people tag the question with the language they want the solution in. It was tagged C++, so I answered in C++, and it's not that big a stretch to convert it to C anyway. – Seth Carnegie Sep 23 '12 at 14:11
1

Removed my downvote. The question was tagged both C and C++, but I edited because in the question text it was clearly stated that the language was C. And, frankly, I'm tired of seeing mixed C/C++ tags when they shouldn't :) – Luchian Grigore Sep 23 '12 at 14:12
@LuchianGrigore yes, it's been so long since I used `new` (especially for multidimensional arrays) that I completely and utterly forgot the syntax for it. Thank you for your patience. – Seth Carnegie Sep 23 '12 at 14:24

score 2 · Answer 2 · edited May 23 '17 at 12:10

2

If you declare this on stack (e.g. in some function) then yes, it will provide stack overflow.

You can declare it as static ('global variable') or allocate memory dynamically.

The Using malloc for allocation of multi-dimensional arrays with different row lengths question is pretty much about it.

edited May 23 '17 at 12:10

Community

1
1

answered Sep 23 '12 at 14:05

dreamzor

5,795
4
41
61

score 2 · Answer 3 · answered Sep 23 '12 at 14:12

2

Here is how you allocate and free a 2D array on the free store in C:

unsigned char (*idata)[1400] = malloc(1600 * 1400);
// ...
free(idata);

answered Sep 23 '12 at 14:12

fredoverflow

256,549
94
388
662

score 0 · Answer 4 · edited Sep 23 '12 at 14:21

0

When you use expressions like unsigned char idata[sz1][sz2], the space of the array is allocated in stack, while the space of the stack is somehow really small, which causes you problem.

But if you use unsigned char* idata = new char*[sz], the space needed is allocated on the heap. Usually you can get the space you want.

edited Sep 23 '12 at 14:21

Prasad S Deshpande

1,362
4
15
35

answered Sep 23 '12 at 14:08

shirley

76
4

Sorry, I didn't realize that he was talking about C exactly. If it's c, you can use functions like malloc. While if it's c++, you can use new. – shirley Sep 23 '12 at 14:11

Is there any limitation on the maximum size of array in c?

4 Answers4

Linked