public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/15592] mtrace.c tr_break() is not called from malloc hooks
Date: Wed, 14 Jul 2021 02:50:42 +0000 [thread overview]
Message-ID: <bug-15592-131-uxYCPswm0m@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15592-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15592
Siddhesh Poyarekar <siddhesh at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
CC| |siddhesh at sourceware dot org
--- Comment #3 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
tr_break has been removed in 2.34.
commit 00d28960c5388a582a0485e07629b553c32dde49
Author: Siddhesh Poyarekar <siddhesh@sourceware.org>
Date: Sat Jul 3 00:47:34 2021 +0530
mtrace: Deprecate mallwatch and tr_break
The variable and function pair appear to provide a way for users to
set conditional breakpoints in mtrace when a specific address is
returned by the allocator. This can be achieved by using conditional
breakpoints in gdb so it is redundant. There is no documentation of
this interface in the manual either, so it appears to have been a hack
that got added to debug malloc. Deprecate these symbols and do not
call tr_break anymore.
Reviewed-by: DJ Delorie <dj@redhat.com>
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-07-14 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 16:53 [Bug malloc/15592] New: " fcollyer at gmail dot com
2013-10-14 16:08 ` [Bug malloc/15592] " neleai at seznam dot cz
2014-01-04 23:20 ` fcollyer at gmail dot com
2014-06-13 15:09 ` fweimer at redhat dot com
2021-07-14 2:50 ` siddhesh at sourceware dot org [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=bug-15592-131-uxYCPswm0m@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).