[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Could --disable-leaks be made a runtime switch?
From: |
Avery Pennarun |
Subject: |
Re: Could --disable-leaks be made a runtime switch? |
Date: |
Tue, 12 Feb 2008 11:06:27 -0500 |
On 12/02/2008, Thomas Dickey <address@hidden> wrote:
> There are a few functions that can be called to free up the "permanent"
> memory, but that's part of the --disable-leaks feature.
If those functions are in the library even without --disable-leaks,
though, you could call them from your app on *any* ncurses binary
distribution on any platform. That would be handy... and I seem to
remember having done it before :)
valgrind is getting to be an indispensable tool for C/C++ developers,
so libraries that don't make it easy to cooperate with valgrind are
kind of a pain. (glibc and openssl are other examples.)
Have fun,
Avery
- Could --disable-leaks be made a runtime switch?, Steve Litt, 2008/02/11
- Re: Could --disable-leaks be made a runtime switch?, Avery Pennarun, 2008/02/12
- Re: Could --disable-leaks be made a runtime switch?, Thomas Dickey, 2008/02/12
- Re: Could --disable-leaks be made a runtime switch?,
Avery Pennarun <=
- Re: Could --disable-leaks be made a runtime switch?, Thomas Dickey, 2008/02/12
- Re: Could --disable-leaks be made a runtime switch?, Avery Pennarun, 2008/02/12
- Re: Could --disable-leaks be made a runtime switch?, Thomas Dickey, 2008/02/12
- Re: Could --disable-leaks be made a runtime switch?, Avery Pennarun, 2008/02/12
- Re: Could --disable-leaks be made a runtime switch?, Stephan Beal, 2008/02/12
- Re: Could --disable-leaks be made a runtime switch?, Steve Litt, 2008/02/12