A few questions about string literals and inputting strings

I'm trying to gain a better intuition on how string literals work in C.

Code:

---

char * c = "hello";

c = "goodbye";

---

After the code segment above completes, what happens to the space in memory where the bytes making up the string "hello" are located? Does that space remain untouchable for the life of the program even though it's no longer accessible, or is it "freed up" the second I assign c = "goodbye"?


Also, what would the following code do?

Code:

---

"howdy";

---

Would it create space for "howdy" and then free it back up right after the statement completes? Are these string literals put into memory at compile time or run time? If it's compile time, does that mean it lives for the life of the program?


Similarly, when you write the statement "char c[30];" are those 30 bytes set aside at compile time or run time? What if the "char c[30];" was declared within a function. What happens when the function completes (and c no longer exists?)? Are the 30 bytes ever "freed up", or are they just sitting there, unable to be used for the rest of the program?



Finally, the following code produces a seg-fault when I run it and enter a single-character string for input, and I'm trying to understand why.

Code:

---

char * c = "hello";

scanf( "%s", c );

---

My current understanding of the above code segment is this: a pointer to a character is declared and given the name c. The base address of the string "hello" is then assigned to c. When I run this, I enter the string "a" as my input, which scanf writes to the location specified by c, which is the base address of "hello". So why does this give me a seg-fault? Shouldn't I be able to input any string that is the same size or smaller than the string "hello"? What am I not thinking about correctly?

Also, in the above example (which was only constructed for learning purposes) for a real program I would replace the "char * c = "hello";" with "char c[100];". Is this the way it's usually done if you're just inputting a string?

I'm very confused. However many questions you feel like answering, I'm grateful.

String literals are never freed. As a matter of fact, it would be wrong to try to do so:

Code:

---

c = "hello";
free( c ); /* wrong */

---

A variable declared in a function, unless specified as static is destroyed when that function ends. Now, there's a difference here:

Code:

---

void foo( void )
{
    char *c = "world";
}

---

When you call foo, the variable c is created. When foo ends, the variable c is destroyed. What it points at however, isn't destroyed or freed. It wouldn't even be freed if you had allocated it dynamically inside that function.

The pointer itself is destroyed when the function ends. What it points at is not.


Quzah.

Most of your questions are compiler/environment-specific. How memory is handled behind the scenes is largely implementation-specific. Some things are optimized right out of existence by the compiler.

String literal like "hello" are not modifiable. Their life time is same as static variable. They'll live as long as program is running.

Quote:

---

"char c[30];" was declared within a function. What happens when the function completes (and c no longer exists?)? Are the 30 bytes ever "freed up", or are they just sitting there, unable to be used for the rest of the program?
,

---

Local variables are allocated on stack. and once function returns they die. Note the same for local scope variable.
That's why returning local variable address is wrong.
eg.

Code:

---

char *foo(void) {
  char c[100];
  ...
  return c;          // wrong!

}

char *p;
 {
  char c[100];
  p = c;
 }                // p is no longer pointing to valid memory.

---

Quote:

---

Also, in the above example (which was only constructed for learning purposes) for a real program I would replace the "char * c = "hello";" with "char c[100];". Is this the way it's usually done if you're just inputting a string?

---

Pointer and array are different things. char c[100] means you have memory to hold 100 char.
char *c means you just have a pointer which is un-initialized. You need to initialize it to point to some memory.

Indeed, these questions are somewhat compiler and platform dependant.

syntax - C++ strings: [] vs. * - Stack Overflow is a good page to explain briefly the difference between char c[] = "hi" and char* c = "hi".

Quote:

---

Originally Posted by itsthemac

Also, what would the following code do?

Code:

---

"howdy";

---

Would it create space for "howdy" and then free it back up right after the statement completes? Are these string literals put into memory at compile time or run time? If it's compile time, does that mean it lives for the life of the program?

---

Whether or not it exists in the executable file at all is compiler dependent. I'd expect most decent optimising compiler/linkers to remove it.

I don't think it could ever incur any run-time overhead.

For char* c = "hello there" --

The compiler will put "hello world" as data into the executable file (where and how depends on the platform). Then in a simple world, when you start executing the program, it will load all of the global variables and string literals before getting to main().

Quote:

---

Similarly, when you write the statement "char c[30];" are those 30 bytes set aside at compile time or run time? What if the "char c[30];" was declared within a function. What happens when the function completes (and c no longer exists?)? Are the 30 bytes ever "freed up", or are they just sitting there, unable to be used for the rest of the program?

---

char c[30] is a proper variable that'll probably be allocated on the stack if it's a local variable. As far as i know the memory will be freed at the end of the function.

Quote:

---

Finally, the following code produces a seg-fault when I run it and enter a single-character string for input, and I'm trying to understand why.

Code:

---

char * c = "hello";

scanf( "%s", c );

---

My current understanding of the above code segment is this: a pointer to a character is declared and given the name c. The base address of the string "hello" is then assigned to c. When I run this, I enter the string "a" as my input, which scanf writes to the location specified by c, which is the base address of "hello". So why does this give me a seg-fault? Shouldn't I be able to input any string that is the same size or smaller than the string "hello"? What am I not thinking about correctly?

---

Your understanding is correct -- the scanf will try to write to the memory where "hello world" is held. But string literals specified in this manner are const, and cannot be modified.
This would fail with a segfault too:

Code:

---


char *c = "hello world";
c[1] = 'a';

---

I believe this is part of the C standard. Certainly some compilers/linkers rely on the non-modifiable-ness of string literals and merge identical strings to save space (I doubt x86 compilers do this, since executable size is rarely a concern).

Quote:

---

Also, in the above example (which was only constructed for learning purposes) for a real program I would replace the "char * c = "hello";" with "char c[100];". Is this the way it's usually done if you're just inputting a string?

---

char *c = "hello"; is fine and good for strings you don't want to modify.

You can use
char c[] = "hello"; to do the same-ish thing and get a modifiable string on the stack (has additional run time overhead of copying the literal onto the stack). You could use scanf on a string defined in this manor.

I'd favour char c[100] or similar -- allocating an appropriate length string for any input that may be read to it. Otherwise you could easily get careless and not have a long enough array for some input. Or of course you can dynamically allocate memory with malloc:

char *c = (char*)malloc(100);

Thank you everyone for the help!