So coming back to our old problem, where we have we are passing one on one variable of stack and one
variable of heap, so how can access it from the current space?
So that is what you have to do is you have to call capato use it twice.
So I am a computer user in the night, so I in the right, you have to call copy from user twice.
So you call the.
And you saw the news about the construct and now you have in the construct.
And indeed, which is of the stack and then the point of the heap, so you have a Bundanon.
We don't have an excellent memory, you have a point using that, using that point that I can again
call.
Copy from using says, I have a used one in this, I have a user point to construct on this.
So we know we have user.
So this is a user point.
So we were just passing it was so.
First recapitulating.
We copy the actual value in this.
And then we call the string.
What was the point then, I can call copy from user again.
I can copy the actual location, which is present in the actual activities in the spring.
So it was, I suppose, a.
I can just say.
Right now is the same Musa's percent.
So Kollapen and I can see and a little we both.
A member of the hip.
Now, remember, off the stack, remember the heat, what will happen if I can see if I terminate the
application with the release function, get called?
An abnormality, something you can see does this in.
So let's see with the close of the final execute and televised response so you can trivialize it is
what caused so many legal process.
Dominik's all the file descriptors which are open will be closed.