diff options
author | tedu <> | 2004-02-02 18:15:52 +0000 |
---|---|---|
committer | tedu <> | 2004-02-02 18:15:52 +0000 |
commit | 88dce049d2200f8e66f2fe6a8c21518b467f3762 (patch) | |
tree | 1bed9325a3c3c775da120f3fe00ae2a6e12393d3 | |
parent | 16b2f3bc4142a41a6cc697a3cd5619dad21beb10 (diff) | |
download | openbsd-88dce049d2200f8e66f2fe6a8c21518b467f3762.tar.gz openbsd-88dce049d2200f8e66f2fe6a8c21518b467f3762.tar.bz2 openbsd-88dce049d2200f8e66f2fe6a8c21518b467f3762.zip |
'F'reeguard doc, as reported missing by brad. nit free thanks to jmc
-rw-r--r-- | src/lib/libc/stdlib/malloc.3 | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/src/lib/libc/stdlib/malloc.3 b/src/lib/libc/stdlib/malloc.3 index 1182256650..ea6344d6a9 100644 --- a/src/lib/libc/stdlib/malloc.3 +++ b/src/lib/libc/stdlib/malloc.3 | |||
@@ -30,7 +30,7 @@ | |||
30 | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | 30 | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF |
31 | .\" SUCH DAMAGE. | 31 | .\" SUCH DAMAGE. |
32 | .\" | 32 | .\" |
33 | .\" $OpenBSD: malloc.3,v 1.33 2003/11/25 12:32:54 jmc Exp $ | 33 | .\" $OpenBSD: malloc.3,v 1.34 2004/02/02 18:15:52 tedu Exp $ |
34 | .\" | 34 | .\" |
35 | .Dd August 27, 1996 | 35 | .Dd August 27, 1996 |
36 | .Dt MALLOC 3 | 36 | .Dt MALLOC 3 |
@@ -192,7 +192,14 @@ at exit. | |||
192 | This option requires the library to have been compiled with -DMALLOC_STATS in | 192 | This option requires the library to have been compiled with -DMALLOC_STATS in |
193 | order to have any effect. | 193 | order to have any effect. |
194 | .Pp | 194 | .Pp |
195 | .It Cm F | ||
196 | .Dq Freeguard . | ||
197 | Enable use after free protection. | ||
198 | Unused pages on the freelist are read and write protected to | ||
199 | cause a segmentation fault upon access. | ||
200 | .Pp | ||
195 | .It Cm G | 201 | .It Cm G |
202 | .Dq Guard . | ||
196 | Enable guard pages and chunk randomization. | 203 | Enable guard pages and chunk randomization. |
197 | Each page size or larger allocation is followed by a guard page that will | 204 | Each page size or larger allocation is followed by a guard page that will |
198 | cause a segmentation fault upon any access. | 205 | cause a segmentation fault upon any access. |