Using realloc() Function in C

By: Charles  

The realloc() function changes the size of a block of memory that was previously allocated with malloc() or calloc(). The function prototype is

void *realloc(void *ptr, size_t size);

The ptr argument is a pointer to the original block of memory. The new size, in bytes, is specified by size. There are several possible outcomes with realloc():

  • If sufficient space exists to expand the memory block pointed to by ptr, the additional memory is allocated and the function returns ptr.
  • If sufficient space does not exist to expand the current block in its current location, a new block of the size for size is allocated, and existing data is copied from the old block to the beginning of the new block. The old block is freed, and the function returns a pointer to the new block.
  • If the ptr argument is NULL, the function acts like malloc(), allocating a block of size bytes and returning a pointer to it.
  • If the argument size is 0, the memory that ptr points to is freed, and the function returns NULL.
  • If memory is insufficient for the reallocation (either expanding the old block or allocating a new one), the function returns NULL, and the original block is unchanged.

Listing below demonstrates the use of realloc().

Using realloc() to increase the size of a block of dynamically allocated memory.

1: /* Using realloc() to change memory allocation. */
3: #include <stdio.h>
4: #include <stdlib.h>
5: #include <string.h>
7: main()
8: {
9:     char buf[80], *message;
11:     /* Input a string. */
13:     puts("Enter a line of text.");
14:     gets(buf);
16:     /* Allocate the initial block and copy the string to it. */
18:     message = realloc(NULL, strlen(buf)+1);
19:     strcpy(message, buf);
21:     /* Display the message. */
23:     puts(message);
25:     /* Get another string from the user. */
27:     puts("Enter another line of text.");
28:     gets(buf);
30:     /* Increase the allocation, then concatenate the string to it. */
32:     message = realloc(message,(strlen(message) + strlen(buf)+1));
33:     strcat(message, buf);
35:     /* Display the new message. */
36:     puts(message);
37:     return(0);
38: }
Enter a line of text.
This is the first line of text.
This is the first line of text.
Enter another line of text.
This is the second line of text.
This is the first line of text.This is the second line of text.

ANALYSIS: This program gets an input string on line 14, reading it into an array of characters called buf. The string is then copied into a memory location pointed to by message (line 19). message was allocated using realloc() on line 18. realloc() was called even though there was no previous allocation. By passing NULL as the first parameter, realloc() knows that this is a first allocation.

Line 28 gets a second string in the buf buffer. This string is concatenated to the string already held in message. Because message is just big enough to hold the first string, it needs to be reallocated to make room to hold both the first and second strings. This is exactly what line 32 does. The program concludes by printing the final concatenated string.

Archived Comments

1. Michaelbus
View Tutorial          By: Michaelbus at 2017-07-11 23:49:42

2. AndrewClula
View Tutorial          By: AndrewClula at 2017-06-15 19:56:18

3. Howardcuh
View Tutorial          By: Howardcuh at 2017-05-30 13:55:05

4. Lestertic
View Tutorial          By: Lestertic at 2017-03-10 16:00:59

5. Never use gets for taking inputs from users. Your program is prone to Buffer Overflows.
View Tutorial          By: Aneesh Dogra at 2012-07-20 04:08:32

6. Shouldn't you call free() on the allocated memory block?
Yes, you should !!!
The examp

View Tutorial          By: Ritchie at 2012-05-09 14:14:49

7. DON'T USE GETS!!!!!!!!!!!!!!! IT'S DANGEROUS!
View Tutorial          By: Caterpillar at 2012-04-23 13:22:42

8. nice explanation
View Tutorial          By: hari priya at 2012-02-23 14:34:43

9. Really clear and lucid explanation abt realloc .... thnx a bunch!!!!!!!!
View Tutorial          By: metarus208 at 2012-01-01 14:25:25

10. Looks good, but don't use gets(). gets() is responsible for the world's problems. Use fgets() and sp
View Tutorial          By: Luke at 2011-11-21 09:03:38

11. You should use malloc() at first time to easily explain realloc().
View Tutorial          By: Lalmani at 2011-10-17 11:24:55

12. Very Very Helpful
Thanks a ton

View Tutorial          By: Zepher at 2011-03-12 11:53:09

13. This is a bad example, it does not check if the allocation of memory worked. Also, you'd normally us
View Tutorial          By: Erik at 2011-02-12 07:16:20

14. Its really a very good and impressive explination!
View Tutorial          By: Shalu Panwar at 2011-01-22 04:36:09

15. Good explanation, but in the example, there is not solved a problem with a lack of memory, does it?
View Tutorial          By: Shima at 2010-11-18 06:24:53

16. good explanation
View Tutorial          By: Naresh Kumar at 2010-10-25 00:28:18

17. Very good
View Tutorial          By: take at 2010-03-29 07:47:01

Most Viewed Articles (in C )

Latest Articles (in C)

Comment on this tutorial