https://www.emblogic.com/blog/03/some-important-things-about-segments/ Embedded System and ARM Training Mon, 07 Oct 2013 04:00:03 +0000 hourly 1 http://wordpress.org/?v=3.9.1 https://www.emblogic.com/blog/03/some-important-things-about-segments/#comment-741 Sat, 28 Apr 2012 07:36:55 +0000 http://emblogic.org/blog/?p=2257#comment-741 hi manoj,
all the functions are allocated memory in text segment not in the data segment. only global and static variabls are allowed to be stored in data segment. The variable of functions are stored in stack.

]]> https://www.emblogic.com/blog/03/some-important-things-about-segments/#comment-688 Thu, 29 Mar 2012 05:20:08 +0000 http://emblogic.org/blog/?p=2257#comment-688 thanx Gaurav..

]]> https://www.emblogic.com/blog/03/some-important-things-about-segments/#comment-684 Tue, 27 Mar 2012 14:29:01 +0000 http://emblogic.org/blog/?p=2257#comment-684 also the memory allocated by malloc is heap …because memory in heap remains till we free it explicitly a program to depict the usefullness of malloc
int* func()
{
int i;i=10;
return(&i);
}
int main()
{
int* ptr;
ptr=func();
printf(“%d”,*ptr);
}when we execute this program it gives a warning …reason being when we are returning the address of i from func then i is a local variable of func which vanishes after func exits ….thus the pointer in the main function becomes a bad pointer that is not pointing towards anything…but if we use int* ptr=(int*)malloc(sizeof(int))
and then use return(ptr); and then dereference the ptr pointer in main we will not get any warning because the memory in heap remains

]]>