tag:blogger.com,1999:blog-2130073091225594073.post7887136236547550954..comments2023-02-26T12:40:35.010+09:00Comments on Reiisi -- 零石: Your Memory Map is No Longer Trivia零石http://www.blogger.com/profile/01111094813708912513noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2130073091225594073.post-16181436506809734262017-07-01T08:26:14.716+09:002017-07-01T08:26:14.716+09:00Between the heap and the stack ...
... depends on...Between the heap and the stack ...<br /><br />... depends on what you are calling the heap.<br /><br />And that is part of the reason we have trouble with things like this, because what one person calls heap is another person's something else.<br /><br />In the above, I'm considering everything not on the stack as on the heap, to simplify the explanation. (I don't know about you, but I run into trouble when I try to explain everything at once.)<br /><br />I mentioned shared objects in the later post, BTW:<br /><br />http://defining-computers.blogspot.com/2017/06/keeping-return-address-stack-separate.html<br /><br />That post will explain more about why I am ranting on this subject.<br /><br />And thanks for mentioning pmap. It would be useful to include in these rants.零石https://www.blogger.com/profile/01111094813708912513noreply@blogger.comtag:blogger.com,1999:blog-2130073091225594073.post-52619361269578156632017-07-01T03:08:12.657+09:002017-07-01T03:08:12.657+09:00Not really clear what your problem is.
As for the...Not really clear what your problem is. <br />As for the gap between the stack and the heap, it is not empty. All the memory mapped shared objects are mapped there, this means that even if you ware allocating on the stack variables so big that they englobe the guerd pages, you would still hit write protected pages.<br />You can check with the pmap command (Unix and Linux) what the memory space of the process looks like.gallier2https://www.blogger.com/profile/04285836062429366578noreply@blogger.com