Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Difference between declared string and allocated string

Tags:

c

I.  char *str = "Stack";

II. char *str = (char*) malloc(6);
    strcpy(str, "Stack");

What are the differences between above two approaches?

Do they are same or something is different behind the curtains?

like image 395
VishalDevgire Avatar asked Apr 15 '13 17:04

VishalDevgire


People also ask

Is string allocated on heap?

In Java, strings are stored in the heap area.

Are Rust strings heap allocated?

Rust has more than only &str s though. A String is a heap-allocated string. This string is growable, and is also guaranteed to be UTF-8.

How does the strings are stored in the memory?

Strings are stored on the heap area in a separate memory location known as String Constant pool. String constant pool: It is a separate block of memory where all the String variables are held. String str1 = "Hello"; directly, then JVM creates a String object with the given value in a String constant pool.

Can you malloc a string?

Use malloc() to allocate storage space for string data.


2 Answers

The code above will cause problems.

The first instance is known as static string allocation and definition. For normal variables like int, etc, and non-string data types, such a declaration would allocate data on the stack. In the case of strings being initialized via string literals (ie: "stack"), it is allocated in a read-only portion of memory.

The string itself should not be modified, as it will be stored in a read-only portion of memory. The pointer itself can be changed to point to a new location.

ie:

char strGlobal[10] = "Global";

int main(void) {
  char* str = "Stack";
  char* st2 = "NewStack";
  str = str2;  // OK
  strcpy(str, str2); // Will crash
}

To be safe, you should actually allocate as a pointer to const data, ie:

const char* str = "Stack"; // Same effect as char* str, but the compiler
                           // now provides additional warnings against doing something dangerous

The second is known as dynamic allocation, which allocates memory on the heap, not the stack. The string can be modified without hassle. At some point, you need to free this dynamically allocated memory via the free() command.

There is a third means of allocating a string, which is static allocation on the stack. This allows you to modify the contents of the array which is holding the string, and it is statically allocated.

char str[] = "Stack";

In summary:

Example:                       Allocation Type:     Read/Write:    Storage Location:
================================================================================
const char* str = "Stack";     Static               Read-only      Code segment
char* str = "Stack";           Static               Read-only      Code segment
char* str = malloc(...);       Dynamic              Read-write     Heap
char str[] = "Stack";          Static               Read-write     Stack
char strGlobal[10] = "Global"; Static               Read-write     Data Segment (R/W)

You should also read up on how data is segmented for applications in modern operating systems. It will really increase your understanding of how your code is being built.

References


  1. Data Segment, Accessed 2013-04-15, <http://en.wikipedia.org/wiki/Data_segment>
  2. Code Segment, Accessed 2013-04-15, <http://en.wikipedia.org/wiki/Code_segment>
like image 90
Cloud Avatar answered Sep 20 '22 17:09

Cloud


In the first case, your pointer Points to a const char* which is allocated in the read only-part of the process-memory.
In the second case, you are allocating memory dynamically and eventuall copy the string "Stack" to your allocated memory.

You must eventually release the memory from II using free.

like image 27
bash.d Avatar answered Sep 23 '22 17:09

bash.d