summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/malloc.3 (follow)
Commit message (Expand)AuthorAgeFilesLines
* zap trailing whitespacetb2023-12-041-2/+2
* Save backtraces to show in leak dump. Depth of backtrace set byotto2023-12-041-8/+10
* correct Va in previous;jmc2023-10-221-2/+3
* When option D is active, store callers for all chunks; this avoidsotto2023-10-221-11/+27
* Document that small allocations are initially junked with 0xdf nowotto2023-07-011-3/+3
* Recommit "Allow to ask for deeper callers for leak reports usingotto2023-06-301-2/+24
* Revert previous, not all platforms allow compilingotto2023-06-231-24/+2
* Allow to ask for deeper callers for leak reports using malloc options.otto2023-06-221-2/+24
* More thorough write-afetr-free checks.otto2023-06-041-9/+11
* remove bad Pp;jmc2023-04-171-3/+2
* Dump (leak) info using utrace(2) and compile the code always inotto2023-04-161-7/+17
* Check all chunks in the delayed free list for write-after-free.otto2023-04-011-3/+4
* man pages: add missing commas between subordinate and main clausesnaddy2022-03-311-4/+4
* Cache implementation has changed, we do not hold on to an exact numberotto2021-04-091-3/+4
* - Make use of the fact that we know how the chunks are aligned, andotto2021-02-251-3/+3
* Add comment line saying S is described vaguely on purpose.otto2019-09-141-2/+3
* clarify that later flags modify earlier flags;schwarze2019-05-191-2/+4
* Mention introduction of *_conceal.otto2019-05-131-2/+8
* Inroduce malloc_conceal() and calloc_conceal(). Similar to theirotto2019-05-101-3/+26
* remove a stray line accidentally left behind in rev. 1.120;schwarze2018-12-051-3/+2
* fold the contents of malloc.conf.5 into malloc.3 and sysctl.2,jmc2018-11-211-6/+118
* Introducing malloc_usable_size() was a mistake. While some otherotto2018-11-211-27/+4
* Implement malloc_usable_size(); ok millert@ deraadt@ and jmc@ for the man pageotto2018-11-181-5/+29
* zap last remains of malloc.conf; prompted by and ok jmc@otto2018-11-081-6/+6
* rm FILES section; prompted by Janne Johanssonotto2018-11-061-7/+2
* Implement C11's aligned_alloc(3). ok guenther@otto2018-11-051-4/+41
* Typo: freezeo -> freezerotb2017-05-151-3/+3
* Rearrange text a bit to make it clear what "discarded" means; ok jmc@ deraadt@otto2017-04-231-8/+13
* consictently use .Dv NULL and a few other tweaks; ok schwarze@otto2017-04-171-20/+17
* allow clearing less than allocated and document freezero(3) betterotto2017-04-131-8/+21
* tweak previous;jmc2017-04-101-4/+4
* Introducing freezero(3) a version of free that guarantees the processotto2017-04-101-24/+58
* Consistentcy between nmembers and size order. From Christopher Hettrick;otto2017-04-061-8/+8
* rephrase more enumerations of functionsotto2017-03-291-13/+10
* Stop enumeration all allocation functions, just say "allocation functions"libressl-v2.5.2otto2017-03-261-32/+13
* document new recallocarray diagnostic; zap a few diagnostics that shouldotto2017-03-241-8/+9
* remove unneccessary macro;jmc2017-03-171-2/+2
* Strengthen description of recallocarray(3) behaviour, hoping that readersderaadt2017-03-171-5/+10
* Some tweaks from jmc@ and describe better what recallocarray does;otto2017-03-071-7/+16
* Introducing recallocarray(3), a blend of calloc(3) and reallocarray(3)otto2017-03-061-6/+64
* malloc does not *need* to return page-aligned objects for size >=otto2017-02-121-5/+2
* avoid sentence splicing;jmc2016-10-201-2/+2
* canary corruption message changed a bitotto2016-10-201-5/+5
* make clear the length printed is the requested lengthotto2016-10-081-3/+3
* grammar fix previous;jmc2016-10-071-2/+2
* document "chunk canary corrupted" errorotto2016-10-071-2/+7
* Document ``use after free'' error messageotto2016-04-031-2/+4
* Remove sentences in RETURN VALUES sections saying that functions withmmcc2016-03-121-6/+2
* Fix err(3) calls after allocation failures in examples.schwarze2016-02-051-8/+8
* Long ago, malloc internally had two kinds of failures, warnings and errors.tedu2016-01-061-6/+3