This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
glibc 2.26 mtrace broken, missing allocations
- From: Stefani Seibold <stefani at seibold dot net>
- To: libc-help at sourceware dot org
- Date: Thu, 05 Apr 2018 22:01:59 +0200
- Subject: glibc 2.26 mtrace broken, missing allocations
Hi,
when using mtrace i get a report of a reallocation which has an address
which was not reported.
For example:
@ /usr/lib64/libgobject-2.0.so.0:(g_signal_newv+0x23d)[0x7ffff7eb409d] - 0x5555559344c0
@ /usr/lib64/libglib-2.0.so.0:(g_malloc+0x19)[0x7ffff7244039] + 0x555555922d40 0x60
@ /usr/lib64/libglib-2.0.so.0:(g_realloc+0x20)[0x7ffff72440f0] < 0x5555558f0ea0
@ /usr/lib64/libglib-2.0.so.0:(g_realloc+0x20)[0x7ffff72440f0] > 0x5555558f0ea0 0x10
@ /usr/lib64/libglib-2.0.so.0:(g_realloc+0x20)[0x7ffff72440f0] < 0x5555558f0e70
The ingoing address 0x5555558f0ea0 for the realloc was not reported by
an other alloc.
The process (gvim -f) is single threaded and it is always the same
address without address layout randomization.
How is this possible? Are there allocation functions which are not
traced by mtrace?
My glibc version:
GNU C Library (Gentoo 2.26-r6 p7) stable release version 2.26, by Roland McGrath et al.
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 7.3.0.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
Native POSIX Threads Library by Ulrich Drepper et al
BIND-8.2.3-T5B