Eric Schrock wrote:
> Are you sure you had UMEM_DEBUG set in your environment? Just linking
> to libumem doesn't enable the debugging flags. What does
> '::getenv -t', '::umem_status', and 'umem_flags/X' show?
>
Yeah, that was my thought that they did not set the environment up
correctly, an
Hi,
I am troubleshooting a memory leak issue and have captured a gcore from
a running process with libumem enabled. It reports something I have
never seen before, and that I could not find any information about.
Here is what findleaks -d reports:
> ::findleaks -d
CACHE LEAKED
Are you sure you had UMEM_DEBUG set in your environment? Just linking
to libumem doesn't enable the debugging flags. What does
'::getenv -t', '::umem_status', and 'umem_flags/X' show?
- Eric
On Tue, Oct 23, 2007 at 03:48:22PM -0400, Peter Shoults wrote:
> Hi,
>
> I am troubleshooting a memory
