From: Stefani Seibold <stefani@seibold.net>
To: libc-help@sourceware.org
Subject: glibc 2.26 mtrace broken, missing allocations
Date: Thu, 05 Apr 2018 20:02:00 -0000 [thread overview]
Message-ID: <1522958519.9141.11.camel@seibold.net> (raw)
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
next reply other threads:[~2018-04-05 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 20:02 Stefani Seibold [this message]
2018-04-05 20:21 ` Carlos O'Donell
2018-04-05 20:33 ` Stefani Seibold
2018-04-05 20:52 ` Carlos O'Donell
2018-04-05 21:01 ` DJ Delorie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1522958519.9141.11.camel@seibold.net \
--to=stefani@seibold.net \
--cc=libc-help@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).