On Mon, Jul 27, 2020 at 2:54 PM Martin Liška <mli...@suse.cz> wrote: > > On 7/27/20 2:51 PM, Richard Biener wrote: > > On Mon, Jul 27, 2020 at 2:50 PM Andreas Schwab <sch...@linux-m68k.org> > > wrote: > >> > >> On Jul 27 2020, Martin Liška wrote: > >> > >>> @Andreas: Is it a known issue? > >> > >> Which issue? > > > > I guess Martin means the checking glibc done looks excessive > > (for the specific case of realloc). But yes, it's enabled in the build roots > > so we just get what we ask for. > > Yes. I'm basically curious who is this enabled/disabled for glibc. > I speak e.g. about: > > #0 0x00007ffff7e886f0 in mem2chunk_check () from /lib64/libc.so.6 > #1 0x00007ffff7e8cb8a in realloc_check () from /lib64/libc.so.6 > #2 0x00005555555550bf in main (argc=<optimized out>, argv=<optimized out>) > at bench.c:7
It's /etc/profile.d/malloc-debug.sh > Martin > > > > > Richard. > > > >> Andreas. > >> > >> -- > >> Andreas Schwab, sch...@linux-m68k.org > >> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 > >> "And now for something completely different." >
