Dynamic Memory Allocation | C Programming Tutorial
Vložit
- čas přidán 10. 07. 2021
- An overview of dynamic memory allocation in C. Source code: github.com/portfoliocourses/c.... Check out www.portfoliocourses.com to build a portfolio that will impress employers!
- Jak na to + styl
Dude, You have helped me a ton more than possible, you explain things so much better than most tutorials out there, Thank you so much!
That’s so great to hear, thanks for sharing this, and you’re very welcome! :-)
Your videos are being of great help to me on my Data Structures and Algorithms class at college. You teach very well, thanks very much!
You're very welcome, I'm so glad to hear these videos are helping you! 😀
Where are u studying?
A lovely explanation from someone who didn't come into this field from the early days.
Man I love your channel. Your explanation is clear and consistent so even I can understand.
thank you so much for this video i've been struggling with malloc and calloc for the longest time and you were the first one that explained it in a way that i understand Love the channel
That's awesome, I'm very glad to hear this video helped you out. 🙂
your teaching way is so clear and easier to listen. Thank you again.
this is top quality content, and yet terribly underrated, thank you for your clear explanation!
You're very welcome, I'm glad you enjoyed the video! :-D
You are a legend, it took me hours trying to understnad this from my teacher and books, but you have summed it up for me in 30 (15 because I like to go fast) min!
Thank you!
You’re welcome Alex, I’m glad the video was able to help you out! :-)
You teach very well, Your videos are very helpful, I hope more people realize the quality of your work.
Thank you for the kind feedback Christopher, I’m glad you enjoy the videos! :-) The channel has only been active for 2 years, I’m hoping over time more people learn about it too.
Time stamps:
intro: 0:00
Stack vs Heap: 0:47
malloc: 5:08
Memory leaks/Manual memory management: 12:22
calloc: 18:09
Memory management: 29:18
cliff-hanger
This was the only good video I could find after watching several videos
Nice job 🥂
I’m glad the video was helpful for you, and thank you for the kind feedback! :-)
That was an awesome tutorial! I followed along on my text editor + Ubuntu terminal and made clarifying comments (for myself, haha). I found the use of the *item pointer in the peek and pop functions as an insightful way to use the addresses to access. Thank you again, fantastic content!
You're very welcome, I'm glad to hear you were able to follow along and that you enjoyed the content! :-)
@@PortfolioCourses Whoops, to clarify, this comment was meant for your Stack ADT and operations tutorial!
@@dangeerraaron Oh ok that makes sense. 🙂
so under rated channel!
Really well explained, thank you for the lesson!
You’re welcome! :-)
lovely video, glad I found this channel
Thank you very much for the kind words, and I'm glad you found the channel too! 🙂
Thank you Sir. Your explanations completely clear all my confusions.
You’re welcome Ashenafi, I’m glad the explanations cleared things up! :-)
This is incredible. I can find all answers that ı have thought about C and C++.
That's excellent to hear Yiğit! :-)
another very illustrative !! thank you
You’re welcome Alvaro! :-)
Man, this is actually entertaining!
I’m glad you enjoyed it! :-)
Very helpful video, thank you!
You're welcome! 😀
Your guides rock!
I’m glad you enjoy them Doruk! :-)
Splendid explanation. Thanks.
You're welcome, I'm glad you enjoyed it! :-)
Excellent video, very helpful, thankyou
You’re very welcome! :-) I’m really glad to hear you enjoyed the video.
You're an awesome tutor! I look forward to when you'll do a video that shows how we can save user's input into a malloc created array!
Thank you Olamide! :-) Once you’ve allocated space for the array with malloc filling it with user input is the same as a regular array (“on the stack”), this video might help you with that: czcams.com/video/5nyMb7hJ7Xs/video.html
@@PortfolioCourses Thank you for responding. I feel so honored. I'll try it and get back to you
@@D_Ladybug You're welcome. And cool sounds good! 🙂
#include
#include
int main () {
int i, n;
int *a;
printf("Number of elements to be entered:");
scanf("%d",&n);
a = (int*)calloc(n, sizeof(int));
printf("Enter %d numbers:
",n);
for( i=0 ; i < n ; i++ ) {
scanf("%d",&a[i]);
}
printf("The numbers entered are: ");
for( i=0 ; i < n ; i++ ) {
printf("%d ",a[i]);
}
free( a );
return(0);
}
awesome tutorial
Great video, thank you!
You're welcome! 🙂
Thank you very much,good sample programs
You're very welcome, I'm glad you enjoyed the sample programs! :-)
@Host
The 'realloc' does apply to 'calloc' as well, correct? I'm pretty sure it does but it wasn't said and I don't want to assume I'm understanding it properly
amazing very clear
Your videos are very clear and educational. This one is particularly interesting. I've coded in numerous languages including C, master of none. I don't even consider myself an expert in any. But I can be proficient. That aside, I found interesting the section where you save the pointer to the allocated memory into the save variable, free(a) then can still access the data in that memory location. For some reason, I thought or read or heard that kernels prevent access to memory not owned by the program. I guess this is not the case. Can the C program change the value once it's been freed? So does that mean that a C program can effectively step through the entire RAM to inspect and/or change the values?
very good informations thank you sir
You're very welcome! :-D
so helpful...thanks
You're welcome! :-)
thank you so much! спасибо
You’re welcome! :-)
great content
Thank you very much Philipp! :-)
Thank you Kevin, thanks
You're welcome Emanuel! :-)
good explanation
Thank you Ishimwe, I'm glad to hear you enjoyed it! :-D
Thank you for the informative video! After trying out the code, I'm a bit confused with the output of the *save pointer because from save [ 0 ] to save [ 3 ], it prints out random numbers and not 5, 4, 3, and 2 as expected, while the rest are just fine. Is this because of my own device or compiler? Thank you
I'm not sure Muhammad. I think you should get the same result. The original code is available here: github.com/portfoliocourses/c-example-code/blob/main/dynamicmem.c. That said, while free() is not required to alter the free'd memory (e.g. setting all the memory to zeros or random data), I don't believe there is anything stopping the compiler/OS/etc from doing this either. So if your using the exact same code and getting a different result, it may be due to the compiler/OS. :-)
@@PortfolioCourses Thank you! The os may have an effect on the result
@@muhammadaushafalfarras2485 hi! I got the exact same problem. [0]to [3] gets random numbers or 0's and after [3] it gave me the correct answers. Did you able to solve the problem?
super helpful tysm..
You're very welcome! :-)
heap and stack are not the only memories in C, there's also static memory
Is there a way to specify the amount of memory you want the whole program to occupy? How does the computer decide how much memory to reserve for the instructions/heap/stack together?
That's a good question Arthur and to an extent the answer is that "it depends on the compiler". :-) Often how exactly a program compiles or is setup to execute isn't something that's part of the language definition, so it's left up to the compiler makers to decide. It can also vary from one platform (OS, hardware, etc) to the next too. So while it's a good question, I'm not sure I can provide a great answer. I think learning about compiler and OS design would help to answer these questions though.
I've always been curious about how malloc deals with new/free allocations of different sizes over time. What does the memory look like over time?
I think some of that depends on the OS / architecture. But memory can definitely become "fragmented" with lots of gaps and whatnot, depending on what you're doing.
Hi, just here to clear things up about realloc. Realloc is essentially copying an old dynamic array and pasting it into a newly allocated dynamic array with a new size? Is the memory in the old dynamic array free up when realloc call? Thanks !
Great question Nathan! :-) And yes, that's the idea. realloc() doesn't always need to copy the old dynamic array to a new location though, it will do that if it can enlarge the exist block of memory at the existing location in memory. If it does need to move the block of memory to a new location, it will copy the data, and it will free the 'old' area of memory for use again. Interestingly though, it may not CLEAR this block of memory, so whatever was there before, like passwords for example, will remain there. You might find these videos interesting:
realloc basics: czcams.com/video/vr7qCQLrUt8/video.html
realloc security vulnerability: czcams.com/video/_Ns0CWEoRio/video.html
handle realloc failure safely: czcams.com/video/skqCnhhA0ZY/video.html
Which programming language has pointers and object oriented programming ?
Java doesn't have pointers but is a oop language
C++ has pointers and OOP. :-)
Java needs an interpreter, it doesn't run natively.
Is it necessary to typecast like:
int *a = (int*) malloc (sizeof(int) * 10)
Because when I didn't include (int*) like in your code, it returns an error.
Great question! 🙂 In C it is not necessary to typecast, but in C++ it is necessary. If you are using a C++ compiler, that might be the reason you get an error.
@@PortfolioCourses okay thank you so much!
@@marbles5590 You're welcome Shannen! 😀
Thanks!
Wow thank you very much! :-)
Interestingly, when I tried the infinite malloc part, it didn't "crash". First the browser window went black. The the whole screen.
Apparently Win10 happily lets you steal memory space from running processes.
It's a feature for glowies to install malware on your devices
how can i make my visual studio look like yours?
btw thanks for the video, i learnt a lot more from this video alone than my college.
Just so the video is focused on code, I go to the view menu at the top, and then the appearance submenu, and then I turn off all the different panels. I make the font bigger, though exactly how big depends on the video, that can be done by searching for 'font' underneath settings. And I use Terminal on MacOS, I just have the terminal next to Visual Studio Code on the right. :-) And I'm very glad to hear this video helped you out!
At 9:36, do we not need to typecast (int *) into malloc since it returns a void pointer? Or is it just considered good practice/readability
Great question! :-) Yes, we don't need the typecast in C because malloc returns a void pointer. In C++ we do use the typecast: stackoverflow.com/a/3477952.
@@PortfolioCourses Ohh thanks!! That part had me confused since C++ does int* arr = new int[n]. Love your videos by the way, trying to learn C before college classes start!!!
Thanks for this awesome video . I am trying to understand the things and I have came up with this question:
Can you explain what is the difference between
int a[10];
vs.
int *a = malloc(sizeof(int) * 10);
Thanks a lot.
You're welcome! :-) The short answer is that the first one is declaring an array on the stack, the second declares a pointer variable called 'a' that will "point to an int". What this means is that it will store the memory address of an int. The malloc() function will allocate enough bytes to store 10 int values, i.e. it will go out and get block of memory large enough to store 10 ints. It returns the memory address of this block of memory, and that gets stored into the variable 'a'. We call this a "dynamically allocated array" and it gets stored in a different place in memory than the stack called "the heap". Learning more about pointers can help to learn about dynamic memory allocation: czcams.com/video/2GDiXG5RfNE/video.html.
@@PortfolioCourses So many thanks to you, great teacher :) You are my most favorite teacher in youtube on my journey of becoming software engineer. Thanks a lot for everything
You're welcome! :-) And thank you so much for sharing such kind feedback, that means a lot to me!
So is airplane systems built with the c programming language? And also NASA systems?
Also is assembly language much faster than c since it talks directly with the machine?
Thanks.. very useful video
I'm not sure what languages those systems are built with. It wouldn't surprise me if they use something "safer" than C, but I don't know. Assembly can be faster than C, but it can also be slower because compilers can be "smarter" about optimizing code execution than programmers sometimes. :-)
It's unclear to me why on slide 4 (~2:45) in the stack table we have *c = 8* and *d = 9* when *myfunction* gets called with *a* and *b,* which are 4 and 7, respectively. Shouldn't we have *c = 4* and *d = 7* there?
No because c,d are variables which are supposed to store the numbers given as arguments when the function is called.
@@0xRAND0M Yeah, and the numbers given as arguments when the function *myfunction* is called in *main* are 4 and 7 respectively.
Hello, I would like to ask you if it's also important to NULL a after free-ing int. If it is or not, could you give me some explenation? Thank you so much for your response
Like we it's not reasonable to use it in calloc because this function makes us sure that it is already clear.. but otoh there are some reasons to use it in malloc? I want to make sure that I understand that :)
Hi Adam, whether setting a pointer to NULL is a good practice or not is something people argue about a bit: stackoverflow.com/questions/1025589/setting-variable-to-null-after-free. :-) I would say that it's a good defensive practice to ensure that other parts of the program can check that the pointer is NULL (i.e. not being used to point to memory at that moment), but it may not really solve the problem it's trying to solve. People generally set the pointer to NULL after free to prevent trying to free the memory twice, but that usually occurs when we have multiple pointers to the same position in memory (e.g. by copying a pointer value to another variable) and then we try to free it two times using two different variables that store that address.
If you want to learn about malloc vs calloc this video may help: czcams.com/video/SKBnxCq3HvM/video.html. :-)
Thanks
You’re welcome! :-)
sir would you please make a video how to use the ide you are using. It is really nice editor. Just make a small video how to use it in windows. Thanks
Great question Nathan! In this video I am using Visual Studio Code. I have disabled some of the standard windows though that allow you to select different files, because in the videos I only want to focus on a single code file (most of the time anyways). The terminal is the other program I am using... the equivalent program on windows would be the command-line (though there are more sophisticated Windows terminals/shells, such as power shell). Maybe one day I can make a video on setting up exactly this 'environment' on Windows and/or a Mac. :-)
At 2:04 - Minor correction(maybe): We are essentially passing the parameters a and b to the function. So, c should be equal to a and so is the case for d and b.
That's true, the illustration on the left was more about showing the idea of "the stack". 🙂
my computer crashed after running that memory loop lol
cool man
Thank you! :-)
good
盧卡斯出現尼可拉斯尼可拉斯尼可拉斯內搭褲了
you can't save data of ''a'' in ''save'' . ''a'' and ''save'' point to the same block of memory ,after you freed "a" , "save" will point to same block of garbage value that "a" point to . doesn't make sense you will get different data from "save" .
I don’t understand your comment, are you just repeating what’s discussed in the video? Or do you have a question? Because in the video I say multiple times that save is storing the same memory address as a. And yes, we don’t get different data from save or a because they are pointing to the same thing. :-)
@@PortfolioCourses sorry my mistake , I just get confused when I copied this program on my pc i din't get same output, I got some garbage data, not the same as you .
Oh OK I see, thank you for the update I was curious. :-)
19:55
17:15, didn't crashed the program but jammed the whole computer hahahahahaahahaha. Scary
Hahaha 🙂
"With great power comes great responsibility."
- The bible, right?
No, dude. Star Trek. Wrath of Kahn.
lol warning running it caused my computer to crash
The code in the video will not cause your computer to crash. :-)
@@PortfolioCourses I swear my screen completely went black from doing it on vs code. I did the 10000000 though. Only thing I could do was reset my pc.
zhin
n n n n n n n n n n