openbsd/src/lib/libc/stdlib/malloc.3, branch OPENBSD_7_9_BASEA mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE2025-06-04T00:38:01+00:00Revert 1.144 of lib/libc/stdlib/malloc.3. It was changed by accident2025-06-04T00:38:01+00:00yasuoka2025-06-04T00:38:01+00:00urn:sha1:0afcce73c60015d8a6f4c42857ca2338ec20ca31
by my previous commit.
Again. Make exit(), fclose(), fflush(), and freopen() comply with2025-06-03T14:15:53+00:00yasuoka2025-06-03T14:15:53+00:00urn:sha1:6ed3a1ddc5d30f8d2745857ce2b60d3f6756aa82
POSIX-2008 requirements for setting the underlying file position when
flushing read-mode streams, and make an fseek()-after-fflush() not
change the underlying file position. This commit fixes some minor
problems of the previous.
previous diff from guenther
Much testing, review, assistence form tb@
ok tb@ millert@ for the previous
ok asou
Delete bad advice about abusing malloc_options = "X" as a production2025-05-27T12:40:37+00:00schwarze2025-05-27T12:40:37+00:00urn:sha1:b1dd45ef5fd4c83b819456f207db22005aee5041
feature to terminate the program when out of memory. Application code
should always handle failure of library functions properly. So if you
want your program to terminate, write something like
| p = malloc(...);
| if (p == NULL)
| err(1, NULL);
and don't abuse malloc_options.
Direction suggested by otto@ after anton@ pointed out that this very old
text still used an outdated data type for malloc_options and potentially
failed to define its value at compile time.
OK otto@
explain more precisely how to initialize malloc_options;2025-05-24T12:47:11+00:00schwarze2025-05-24T12:47:11+00:00urn:sha1:e1e8eb89cfa75c5c887a549a6ff37606a00692e7
OK deraadt@
When commons were deprecated, noone noticed that malloc_options in static2025-05-23T00:40:05+00:00deraadt2025-05-23T00:40:05+00:00urn:sha1:5afc322de251083f4ccbab856f6e967161f647d6
binaries had become unlinkable. Change the libc definition to weak to solve
that, and to "const char * const" so that noone will try to set it late.
It must be stable before the first malloc() call, which could be before
main()...
discussion with otto, kettenis, tedu
mkostemp(3) and reallocarray(3) are in POSIX-2024:2024-08-03T20:09:24+00:00guenther2024-08-03T20:09:24+00:00urn:sha1:fbb1d5770a6430778ae6b181693bbf2d9fa8b4a8
adjust #include visibility and update the reallocarray(3) manpage
ok millert@
zap trailing whitespace2023-12-04T22:52:41+00:00tb2023-12-04T22:52:41+00:00urn:sha1:66797a97d1a1d8ba295415e8180bdb9e50016543Save backtraces to show in leak dump. Depth of backtrace set by2023-12-04T07:01:45+00:00otto2023-12-04T07:01:45+00:00urn:sha1:1589284523a88647318588e6ee3aaa968b3bc5e1
malloc option D (aka 1), 2, 3 or 4. No performance impact if not
used. ok asou@
correct Va in previous;2023-10-22T14:04:52+00:00jmc2023-10-22T14:04:52+00:00urn:sha1:dac6e2f568f45af4bd8051bfafbd95b5ec65c73eWhen option D is active, store callers for all chunks; this avoids2023-10-22T12:19:26+00:00otto2023-10-22T12:19:26+00:00urn:sha1:5fb161ca99c3827ce96bd2eafb54ade287c31caf
the 0x0 call sites for leak reports. Also display more info on
detected write of free chunks: print the info about where the chunk
was allocated, and for the preceding chunk as well.
ok asou@