how can I write code to test a[100];

I write some codes as follows:

Code:

---

int main()
{
  int a[2];
  a[0] = 1;
  a[1] = 1;
 
  return 0;
}

---

If my printing code is as follow:

Code:

---

printf("%d\n",a[100]); //a[100] not defined

---

The result is "segmentation fault";

how can I write code to test a[100];
(I means if a[100] is defined, print
if a[100] is not defined, printf("a[100] is not defined.\n");)

how can I come true?

Look at the C library pages for sizeof();

And... please don't start multiple threads for the same question... the mods here don't like it.

C doesn't keep you from wandering around in memory you shouldn't be wandering in. You have to do that yourself.

Quzah.

To find how many elements are in an array you can use...

Code:

---

// declare array
int array[100];
int sarray;

// how many elements?
sarray = (sizeof(array) / sizeof(array[0]));

---

BUT... this only works for static arrays, it's not going to work with arrays created with mallloc. Those you have to keep track of yourself. Quzah is exactly correct... C doesn't prevent buffer overruns or attempting to read/write data outside of array bounds.

Quote:

---

Originally Posted by CommonTater

Look at the C library pages for sizeof();

And... please don't start multiple threads for the same question... the mods here don't like it.

---

It's my mistake for starting multiple threads for the same question!

Quote:

---

Originally Posted by quzah

C doesn't keep you from wandering around in memory you shouldn't be wandering in. You have to do that yourself.

Quzah.

---

I see!

my means is that how to test one data structure whether be defined.( how to test the data which will be printed whether is out of memory )

Code:

---

char *string =  (char*) malloc ( 100*sizeof(char));

// 1000 is my on purpose, though 100 is defined.
for ( int i = 0; i < 1000; ++i )
{
        //my test code is that,but I don't know whether is right
        if ( string[i] )
        {
                  printf("%c,",string[i]);
        } else
        {
                    printf("error of memory.\n"); exit(1);
          }
}

---

Quote:

---

Originally Posted by CommonTater

To find how many elements are in an array you can use...

Code:

---

// declare array
int array[100];
int sarray;

// how many elements?
sarray = (sizeof(array) / sizeof(array[0]));

---

BUT... this only works for static arrays, it's not going to work with arrays created with mallloc. Those you have to keep track of yourself. Quzah is exactly correct... C doesn't prevent buffer overruns or attempting to read/write data outside of array bounds.

---

thanks for your answer. It is good for me.

Quote:

---

Originally Posted by quzah

C doesn't keep you from wandering around in memory you shouldn't be wandering in. You have to do that yourself.

Quzah.

---

Code:

---

#include <stdio.h>
#include <stdlib.h>
char*  fillData()
{
        char *fd = (char*) malloc ( 100*sizeof(char));
        for ( int i = 0; i < 100; ++i )
        {
                fd[i] = 'A';
        }
        return fd;
}
char** createTwoDimArray()
{
        char **ptr = (char**) malloc ( 100 * sizeof(char*) );
        for ( int i = 0; i < 100; ++i )
        {
                *(ptr+i) = fillData();
        }
        return ptr;
}
void print(char **p)
{
        for ( int i = 0; i < 1000; ++i )
        {
                printf("line:%d\n",i);
                for ( int j = 0; j < 1000; ++j )
                {
                      if( p[i][j] != NULL ) { printf("%c,",p[i][j]); }else { break; }
                }
                printf("\n");
        }
}
int main()
{
              char **p = createTwoDimArray();
              print(p);

              return 0;
}

---

why segmentation fault?
1000 can not be modified. It's written on purpose
How to modify the red codes to skip this error? ( how to identify the overruns? )

With just having a pointer, you can't know where you're allowed to go from there.


Quzah.

There is no way for a program to identify down to the byte level whether a particular memory access constitutes an array overrun.

Lets say your OS has a page size of 1K. When you do a particular memory allocation, you get a pointer to the start of a page, so
char *p = malloc(100);

1. The valid subscripts are 0 to 99.
2. Anything from 100 to 1023 is an array overrun, but the OS doesn't care as it is still within the same page.
3. But try p[1024], and that would be a reference to another page - one that doesn't exist. At that point, you get your segfault.

Tools like valgrind and electric fence can help you to locate a lot of case 2.

You could also use man page sigaction section 2 to write a handler for the segfault, though what you could do about it is debatable. You certainly couldn't just ignore it.

Tell us what the actual assignment is and we'll tell you what you're doing wrong. I'm assuming it is one of the "here's a function, now write the rest of the program" variety, but we need to know the actual conditions to help you.

Quote:

---

Originally Posted by Salem

There is no way for a program to identify down to the byte level whether a particular memory access constitutes an array overrun.

Lets say your OS has a page size of 1K. When you do a particular memory allocation, you get a pointer to the start of a page, so
char *p = malloc(100);

1. The valid subscripts are 0 to 99.
2. Anything from 100 to 1023 is an array overrun, but the OS doesn't care as it is still within the same page.
3. But try p[1024], and that would be a reference to another page - one that doesn't exist. At that point, you get your segfault.

Tools like valgrind and electric fence can help you to locate a lot of case 2.

You could also use man page sigaction section 2 to write a handler for the segfault, though what you could do about it is debatable. You certainly couldn't just ignore it.

---

I like this answer. It is better

Quote:

---

Originally Posted by msh

Tell us what the actual assignment is and we'll tell you what you're doing wrong. I'm assuming it is one of the "here's a function, now write the rest of the program" variety, but we need to know the actual conditions to help you.

---

Sometimes, when my program runs, there is a error "segmentation error", but I don't know why and where is the error. I want to handle this error, but I don't know how to do handling.

Do you understand my meaning?

Quote:

---

Originally Posted by zcrself

Sometimes, when my program runs, there is a error "segmentation error", but I don't know why and where is the error. I want to handle this error, but I don't know how to do handling.

Do you understand my meaning?

---

You can run your program in a debugger like "gdb". When the debugger encounters segfault, it will tell you what line of code the problem is.
If you don't want to do that. Try to predict what parts of your program may cause that problem, and use printf to print out a statement before and after these sections are executed.

It's just better to use the debugger.

Quote:

---

Originally Posted by nimitzhunter

You can run your program in a debugger like "gdb". When the debugger encounters segfault, it will tell you what line of code the problem is.
If you don't want to do that. Try to predict what parts of your program may cause that problem, and use printf to print out a statement before and after these sections are executed.

It's just better to use the debugger.

---

java language has try-catch function,
what does C language has?

Can "try-catch" function handle the error "segmentation fault"