Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
C Programming
Is it time for secure C ?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
Reply to thread
Message
[QUOTE="Malcolm, post: 2379822"] On many platforms this is probably what will happen, since the block you have just freed is at the top of the "free list", which was why it was allocated by the first malloc(). However we're discussing implementing "secure C" by adding bounds information to pointers and the like. One thing you would naturally do is rewrite malloc() to ensure that this problem can't happen, though exactly how you would achieve that is anyone's guess. [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
C Programming
Is it time for secure C ?
Top
