Browse Source

remove incorrect statement. the standard *does* require calloc to check

for overflow. stop talking about old broken systems, there's little use
for such info.
OPENBSD_5_8
tedu 9 years ago
parent
commit
e87c880491
1 changed files with 2 additions and 7 deletions
  1. +2
    -7
      src/lib/libc/stdlib/malloc.3

+ 2
- 7
src/lib/libc/stdlib/malloc.3 View File

@ -30,9 +30,9 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE. .\" SUCH DAMAGE.
.\" .\"
.\" $OpenBSD: malloc.3,v 1.89 2015/01/08 03:41:14 deraadt Exp $
.\" $OpenBSD: malloc.3,v 1.90 2015/03/14 08:07:17 tedu Exp $
.\" .\"
.Dd $Mdocdate: January 8 2015 $
.Dd $Mdocdate: March 14 2015 $
.Dt MALLOC 3 .Dt MALLOC 3
.Os .Os
.Sh NAME .Sh NAME
@ -437,11 +437,6 @@ other conforming implementations may return
.Dv NULL .Dv NULL
in this case. in this case.
.Pp .Pp
The standard does not require
.Fn calloc
to check for integer overflow,
but most modern implementations provide this check.
.Pp
The The
.Ev MALLOC_OPTIONS .Ev MALLOC_OPTIONS
environment variable, the file environment variable, the file


Loading…
Cancel
Save