From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: stefani@seibold.net, libc-help@sourceware.org
Subject: Re: glibc 2.26 mtrace broken, missing allocations
Date: Thu, 05 Apr 2018 21:01:00 -0000 [thread overview]
Message-ID: <xnvad5id0y.fsf@greed.delorie.com> (raw)
In-Reply-To: <33298b52-27e5-636b-03e2-799be2b9c0f5@redhat.com> (carlos@redhat.com)
"Carlos O'Donell" <carlos@redhat.com> writes:
> DJ, You've been poking at this area, any thoughts?
The only thing I can think of off-hand is, that it's a malloc that
happened before mtrace() was called. This can happen if, for example,
there's a ctor/init function that's called before main().
Using ltrace to find any pre-mtrace allocs might be fruitful.
Or my malloc trace branch, which hooks sooner than main().
prev parent reply other threads:[~2018-04-05 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 20:02 Stefani Seibold
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 [this message]
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=xnvad5id0y.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=carlos@redhat.com \
--cc=libc-help@sourceware.org \
--cc=stefani@seibold.net \
/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).