Simple Memory Content Question

Hi folks,

I use memcpy to copy a content from a memory location to another

Code:

---

#include <stdio.h>
#include <string.h>

int main ()
{
  char str1[]="Sample string";
  char str2[40];
  char str3[40];
  memcpy (str2,str1,strlen(str1)+1);
  memcpy (str3,"copy successful",16);
  printf ("str1: %s\nstr2: %s\nstr3: %s\n",str1,str2,str3);
  return 0;
}

---

Printf will show the exact same "Sample String" as expected, but if i change printf to

Code:

---

printf ("str1: %X\nstr2: %X\nstr3: %X\n",str1,str2,str3);

---

I get something like

str1: BFBF4962
str2: BFBF493A

I thought the content should be similar? Can anyone help explain it to me please?

Thanks in advanced.

Why did you think the result would be similar? What do you think %X means to printf?

X prints out the value of an unsigned int in hex notation. Do you know what the values printf is showing you are? Hint: What is the difference between the two (BFBF4962 - BFBF493A = what )?

Hi citizen and jason_m,

Thanks for replying. I know what %X does but I tought after copying the content from one location to another, the contents in both location should be exactly the same.

I tought the resulting machine instruction will load the exact bit patterns from the source address and put it into the destination address.

Shouldn't str1 and str2 have the same contents regardless what kind of representation I use for printing the values wether in string, hex or int form...? why does the two values differ in hex representations but not in string form?

Thanks for taking the time to reply to my silly questions :)

Because those arrays decay to pointers and pointers contain a memory address. You're printing the memory address.
If the memory address was not the same, it would be the same array or variable which would make no sense. Because you're creating two different arrays, and then copying the contents into each other.

So to sum it up: they have the same contents, but they are different arrays, so the memory address is different.
(You can't expect to take two mugs, one full of beer, then pour the beer into the other mug and place them at the exact same location [x, y, z]. It's impossible, and it's likewise impossible in the computer world [x, y, z being the memory address].)

Quote:

---

Originally Posted by azzuwan

Shouldn't str1 and str2 have the same contents regardless what kind of representation I use for printing the values wether in string, hex or int form...? why does the two values differ in hex representations but not in string form?

---

The real issue here is that when you pass a string to printf() [or any other function for that matter], you actually just pass the location of the string. Inside printf, the different %letter combinations will then take the respective argument and do the relevant display operation.

In the case of %s, it does something like this:

Code:

---

  case 's':
    char *str = getnextargument();
    while(*str) 
    {
        putchar(*str);
        str++;
    }
    break;

---

in another place you'd find the %x code:

Code:

---

    case 'X':
      usecapitals = 1;
    case 'x':
      unsigned int val = getnextargument();
      char buffer[9];
      // Convert x to a string in buffer, using base 16.
      num2str(buffer, x, 16, usecapitals);
      puts(buffer);
      break;

---

The above code is heavily simplified, and both of these cases are probably 3-5x longer in a real printf implementation, mostly to handle width and right/left positioning.

But as you can perhaps figure out, getnextargument() is a generic function to pick up the next of the arguments, and printf itself DOESN'T know what the next argument represents in itself, it just sees the numeric value as a value that it prints in the form that you've asked for.

If you print a string as %X, it will show you the address of the string, not the string itself, as hex.

--
Mats

Great explanations!

I'm an example of one of those people who started learning programming using "managed environment" language / platform. Totally messed things up when tasked to do things in a language that allows power and control over everything such as C.

Thank you all , especially Elysia and Matsp.
That cleared things up for me.

Just a thought, but if you want more features that are available in managed environment while still remaining close to the hardware, try C++, since it's an evolution of C.