Your message dated Sun, 3 Mar 2013 16:23:07 -0800
with message-id <[email protected]>
and subject line Re: libc6: malloc_stats and mallinfo gives wrong values with
memory-allocatiion >4GB on amd64
has caused the Debian Bug report #336608,
regarding libc6: malloc_stats and mallinfo gives wrong values with
memory-allocatiion >4GB on amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
336608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336608
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libc6
Version: 2.3.5-6
Severity: important
Both functions mallinfo and malloc_stats (malloc.h) report wrong
allocation sizes while allocating more that 4GB on amd64 machines. Since
the struct mallinfo-structure consists of integer there must be some
error converting the values from the kernel into libc. Other processes
like ps or top give correct results.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.4
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Oliver-Mark,
In 2005, Oliver-Mark Cordes wrote:
> Both functions mallinfo and malloc_stats (malloc.h) report wrong
> allocation sizes while allocating more that 4GB on amd64 machines. Since
> the struct mallinfo-structure consists of integer
[...]
Yep, that's exactly the problem. The ABI uses a 32-bit integer, when
a 64-bit value would be more appropriate.
As described upstream, this is known and not likely to change, so I'm
closing this report. That said, thanks for reporting, and given an
example use case or a way forward I'd be happy to reopen it and
propose introduction of a better additional interface upstream.
Sincerely,
Jonathan
--- End Message ---
