{"id":3831,"date":"2019-11-09T00:01:39","date_gmt":"2019-11-09T08:01:39","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=3831"},"modified":"2019-11-16T08:43:13","modified_gmt":"2019-11-16T16:43:13","slug":"playing-with-memory","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=3831","title":{"rendered":"Playing with Memory"},"content":{"rendered":"

Gone are the old days when your C program ruled the entire computer’s domain. Back then, you could access any chunk of memory in the computer, manipulate it in all sorts of interesting ways, and not be concerned that your code’s actions would be restricted. Ah, those were good times.
\n
\nOf course, such freedom meant your program could tear down the entire system. This danger didn’t seem to be a concern back in the day. Still, within its allocated memory chunk, your C code today can manipulate memory in all sorts of interesting ways. The key function is memcpy()<\/em>:<\/p>\n

void * memcpy(void *restrict dst, const void *restrict src, size_t n);<\/code><\/p>\n

Defined in the string.h<\/code> header file, the memcpy()<\/em> or “mem-copy” function copies n<\/code> bytes of storage from memory location src<\/code> to memory location dst<\/code>. Both locations must be allocated in your code; you can’t specify direct storage addresses.<\/p>\n

One common place I’ve seen memcpy()<\/em> used is to duplicate a structure:<\/p>\n

\r\n#include <stdio.h>\r\n#include <stdlib.h>\r\n#include <string.h>\r\n\r\nint main()\r\n{\r\n    struct person {\r\n        int age;\r\n        char name[12];\r\n    } man = { 34, \"George\" };\r\n    struct person *guy;\r\n\r\n    \/* output the structure *\/<\/span>\r\n    printf(\"%s is %d years old\\n\",man.name,man.age);\r\n\r\n    \/* allocate the buffer *\/<\/span>\r\n    guy = (struct person *)malloc( sizeof(struct person) );\r\n    if( guy==NULL )\r\n    {\r\n        fprintf(stderr,\"Unable to allocate memory\\n\");\r\n        exit(1);\r\n    }\r\n\r\n    \/* copy memory *\/<\/span>\r\n    memcpy(guy,&man,sizeof(struct person));\r\n\r\n    \/* output the duplicate structure *\/<\/span>\r\n    printf(\"%s is %d years old\\n\",guy->name,guy->age);\r\n\r\n    return(0);\r\n}<\/pre>\n
The struct person<\/em> variable man<\/code> is defined and declared right away. Its member’s values are output.<\/p>\n
The malloc()<\/em> function allocates a chunk of memory, guy<\/code>, then memcpy()<\/em> duplicates the contents of the man<\/code> variable into the newly-allocated guy<\/code> chunk.<\/p>\n
Finally, the guy<\/code> buffer’s output is displayed, which is identical to the original:<\/p>\n
George is 34 years old
\nGeorge is 34 years old<\/code><\/p>\n
Of course, all this action is a bit much. You could just duplicate the structure from one variable to another, as this variation on the code demonstrates:<\/p>\n
\r\n#include <stdio.h>\r\n\r\nint main()\r\n{\r\n    struct person {\r\n        int age;\r\n        char name[12];\r\n    } man = { 34, \"George\" };\r\n    struct person guy;\r\n\r\n    \/* output the structure *\/<\/span>\r\n    printf(\"%s is %d years old\\n\",man.name,man.age);\r\n\r\n    \/* copy structure *\/<\/span>\r\n    guy = man;\r\n\r\n    \/* output the duplicate structure *\/<\/span>\r\n    printf(\"%s is %d years old\\n\",guy.name,guy.age);\r\n\r\n    return(0);\r\n}<\/pre>\n
This version is shorter, and it does the same thing: guy = man<\/code> takes care of everything.<\/p>\n
The true advantage of memcpy()<\/em> is that it can duplicate the contents of memory into a void<\/em> buffer. Once there, you can examine it as raw data or however you please. I cover this process in next week’s Lesson<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
The memcpy<\/em> function allows chunks of memory to be copied hither and thither, which can lead to some interesting results. Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-3831","post","type-post","status-publish","format-standard","hentry","category-main"],"_links":{"self":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3831","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3831"}],"version-history":[{"count":6,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3831\/revisions"}],"predecessor-version":[{"id":3861,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3831\/revisions\/3861"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3831"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3831"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}