On May 19 16:46:44, schwa...@usta.de wrote:
> >> The current "increase/decrease" wording in malloc(3)
> >> can suggest it has a memory. For example, setting
> >>
> >> vm.malloc_conf=J
> >>
> >> "increases" junk level to two;
> >> does setting
> >>
> >> vm.malloc_conf=C
> >>
> >> later retain a junk level of two,
> >> as there is no 'j' to "decrease" it,
> >> or is the junk level the defult of one now?
>
> Your question makes no sense whatsoever.
>
> First, the word "later" makes no sense.
I should have worded more clearly. I meant programs that start later,
after vm.malloc_conf is set to something else.
It makes perfect sense now, thanks.
Jan
> Malloc initialization is
> only done once during a run of any given program.
> contains J during startup, that is what governs program behaviour.
> Changing the sysctl later no longer has any effect on the running
> program.
> Index: malloc.3
> ===================================================================
> RCS file: /cvs/src/lib/libc/stdlib/malloc.3,v
> retrieving revision 1.124
> diff -u -r1.124 malloc.3
> --- malloc.3 13 May 2019 06:04:55 -0000 1.124
> +++ malloc.3 19 May 2019 14:39:30 -0000
> @@ -270,6 +270,8 @@
> in the program.
> Each is scanned for the flags documented below.
> Unless otherwise noted uppercase means on, lowercase means off.
> +During initialization, flags occurring later modify the behaviour
> +that was requested by flags processed earlier.
> .Bl -tag -width indent
> .It Cm C
> .Dq Canaries .
>
