|
From: Julian S. <js...@ac...> - 2005-11-15 19:18:39
|
Anybody object if I get rid of this? It's out of place in a user manual, and it's also out of date, and I can't be bothered to pull it up to date. But mostly - it's out of place - just confusing clutter for end-users to wade through. J |
|
From: Nicholas N. <nj...@cs...> - 2005-11-15 19:33:45
|
On Tue, 15 Nov 2005, Julian Seward wrote: > Anybody object if I get rid of this? It's out of place in a user > manual, and it's also out of date, and I can't be bothered to pull > it up to date. But mostly - it's out of place - just confusing > clutter for end-users to wade through. I agree. Also, in the limitations just before that -- does Emacs work now? And we should remove the bit about no platform-specific limitations for 2.4.0. N |
|
From: Julian S. <js...@ac...> - 2005-11-15 19:45:04
|
> Also, in the limitations just before that -- does Emacs work now? It does on non-malloc/free-replacing tools. On mc it still fails. I think the problem is that mallinfo() isn't well enough emulated. > And we > should remove the bit about no platform-specific limitations for 2.4.0. Already rm'd. J |
|
From: Nicholas N. <nj...@cs...> - 2005-11-15 19:51:40
|
On Tue, 15 Nov 2005, Julian Seward wrote: >> Also, in the limitations just before that -- does Emacs work now? > > It does on non-malloc/free-replacing tools. On mc it still fails. > I think the problem is that mallinfo() isn't well enough emulated. The hooks are there now -- it's just a matter of filling in m_mallocfree.c:VG_(mallinfo)() and putting in the appropriate increments/decrements throughout m_mallocfree.c. See http://bugs.kde.org/show_bug.cgi?id=110128 for more details, if anyone's feeling inspired to fix it. Nick |