Overflow and bytes

[Ramsin]

Sizeof(a) must be 4 bytes, but why does the overflow occur when I enter at least over 32 characters?!

// HHHe...
#include <iostream>
using namespace std;

int main() {
	char a[4];
	string str;
	
	cin >> str;
	cin.ignore();
	
	int i;
	for(i=0; i<(str.length()); i++) {
		a[i] = *(str.c_str()+i);
	}
	
	/* char * p = &(a[7])+i;
	cout << *p << endl; */
}

Thanks for help...

[johny10151981]

yes your char array variable is 4 bytes. it mean it only can hold 3 character and the 4th character will be used null terminating character. you can also use array a cleverly to hold just 4 byts character.

and why do you think that array will hold 32 character? one byte can hold only one character. One byte mean 8 bit (depending on processor) but its never 8 character

[Ramsin]

(gdb) run
Starting program: /home/ramsin/Desktop/a.out 
AAAABBBBCCCCDDDD

Program exited normally.
(gdb) r
Starting program: /home/ramsin/Desktop/a.out 
AAAAAAAABBBBBBBBCCCCCCCCDDDDDDDD 

Program exited normally.
(gdb) r
Starting program: /home/ramsin/Desktop/a.out 
AAAAAAAABBBBBBBBCCCCCCCCDDDDDDDDF

Program received signal SIGSEGV, Segmentation fault.
0x00272c49 in __libc_start_main () from /lib/libc.so.6

[Oralloy]

Ramsin,

What is happening is that you are blindly writing on the stack, and for whatever reason have 30-something bytes that you can destroy before you reach a critical value.

The error is because you have corrupted a stack framing pointer or a return address; thus, when the execution leaves your main() function, the CPU tries to access memory that is not in your assigned memory space. Thus the segmentation fault.

The reason you get 32 characters is system and complier dependant. On some systems you might only get five characters before having troubles.

So yes, you can easily exceed the bounds of variables using C/C++. In fact, some programs intentionally use the programmer's knowledge of memory lay-out in order to function correctly. However, if you aren't writing high-performance binary communication protocols, you probably don't need to do such things. Just say "No!".

I hope this helps you a little.

Cheers,
Oralloy

[Ramsin]

I thought it was also system/compiler dependant, but I was unsure. Anyway, I must learn about such things, because it's necessary to clearly understand how memory works.

[Oralloy]

Ramsin,

Memory schemes depend on what level you have to know it at. There is a huge difference between using new/delete and what the operating system has to do to allocate virtual memory.

At the risk of confusing you - understand what it is you need to know about memory.

If you are doing application programming, that's one thing.

If you are doing binary network communication, that's another.

If you are writing an operating system, that is yet another.

Stay current with your coursework and you should be fine.

When you write you programs, never assume that you can go outside the boundaries of the memory allocated to your program. Once you do, you immediately enter the realm of system and compiler specific behaviour.

Good Luck!
Oralloy