public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug malloc/208] mallinfo returns incomplete information
Date: Tue, 20 Mar 2012 20:41:00 -0000 [thread overview]
Message-ID: <bug-208-131-dl60ey9Q1U@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-208-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=208
Paul Pluzhnikov <ppluzhnikov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |ppluzhnikov at google dot
| |com
Component|libc |malloc
Resolution|WONTFIX |
Target Milestone|--- |2.16
--- Comment #3 from Paul Pluzhnikov <ppluzhnikov at google dot com> 2012-03-20 18:33:55 UTC ---
8 years later, mallinfo() still actively lies to 32-bit applications, and no
new interface has emerged ;-(
http://cygwin.com/ml/libc-alpha/2011-08/msg00116.html
http://cygwin.com/ml/libc-alpha/2012-03/msg00782.html
Re-opening in hope that this PR can be re-considered.
FWIW, the use case I have is a 32-bit java/JNI application, that wants to use
mallinfo() for out-of-memory self-diagnostics.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next parent reply other threads:[~2012-03-20 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-208-131@http.sourceware.org/bugzilla/>
2012-03-20 20:41 ` ppluzhnikov at google dot com [this message]
2012-03-21 12:20 ` carlos_odonell at mentor dot com
2012-03-22 15:28 ` mtk.manpages at gmail dot com
2012-05-07 20:47 ` aj at suse dot de
2012-05-07 20:52 ` ppluzhnikov at google dot com
2012-05-07 21:16 ` aj at suse dot de
2012-05-15 16:52 ` ppluzhnikov at google dot com
2012-05-16 23:51 ` ppluzhnikov at google dot com
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-208-131-dl60ey9Q1U@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).