On Thu, Mar 30, 2006, Claus Assmann wrote:
application behaves fine. Hence I'm wondering whether there is a
memory leak in some library or the OS, which also could be triggered
by the way my application uses it (see the recent thread about
Thanks to all of you who offered suggestion how to
On 3/30/06, Claus Assmann [EMAIL PROTECTED] wrote:
Is there some simple way to find a memory leak in some OS supplied
library? I have a (constantly running) application that grows in a
week from 5MB to 15MB in size (VSZ and RSS as reported by ps). The
application can be compiled with an
On Fri, Mar 31, 2006, Ted Unangst wrote:
Note: the memory leak seems to be unique to OpenBSD (3.8 and earlier),
just to confirm something, this happens with openbsd 3.7? 3.6?
3.7: yes; 3.6 probably yes, but I don't have statistics from
that time. Here's one from last year:
Tue Sep 6
BTW: it does not seem to be a problem with mutex/cond: I saved
those in an array for reuse (instead of calling _init()/_destroy()
for every invocation) and even then the size grows. I'll try to
build a debugging version of libc (with some malloc checks) over
the weekend.
Another old trick is
Hi!
On Fri, Mar 31, 2006 at 04:58:28PM -0800, Claus Assmann wrote:
On Fri, Mar 31, 2006, David Higgs wrote:
Another old trick is to let your program eat memory for a good while,
and then break into its execution. Randomly inspect some of the
allocated memory your program still holds; there
On Sat, Apr 01, 2006, Hannah Schroeter wrote:
I'm not sure whether there is a map in OpenBSD's malloc. However,
you could of course change it to output trace stuff similar to what I
described in my other mail, and then couple that trace stuff with gdb
debugging.
I plan to do something like
Is there some simple way to find a memory leak in some OS supplied
library? I have a (constantly running) application that grows in a
week from 5MB to 15MB in size (VSZ and RSS as reported by ps). The
application can be compiled with an optional debugging memory
allocator that tracks all
On 3/30/06, Claus Assmann [EMAIL PROTECTED] wrote:
Is there some simple way to find a memory leak in some OS supplied
library? I have a (constantly running) application that grows in a
week from 5MB to 15MB in size (VSZ and RSS as reported by ps). The
application can be compiled with an
On 3/30/06, Claus Assmann [EMAIL PROTECTED] wrote:
Is there some simple way to find a memory leak in some OS supplied
library? I have a (constantly running) application that grows in a
week from 5MB to 15MB in size (VSZ and RSS as reported by ps). The
application can be compiled with an
On Thu, Mar 30, 2006, Ted Unangst wrote:
particular to pthreads, if you are using mutexes or somesuch on the
stack, you will leak memory. (the lock on the stack is just a
pointer, it gets allocated on first use).
All mutexes are part of structures that are allocated via malloc().
Would those
On Thu, Mar 30, 2006, Toni Spets wrote:
On 3/30/06, Claus Assmann [EMAIL PROTECTED] wrote:
Note: the memory leak seems to be unique to OpenBSD (3.8 and earlier),
I can't reproduce it on SunOS 5.9 and others. That's why I'm asking
...
http://valgrind.org/
Thanks for the suggestion (also
On 3/30/06, Claus Assmann [EMAIL PROTECTED] wrote:
On Thu, Mar 30, 2006, Ted Unangst wrote:
particular to pthreads, if you are using mutexes or somesuch on the
stack, you will leak memory. (the lock on the stack is just a
pointer, it gets allocated on first use).
All mutexes are part of
On Thu, Mar 30, 2006, Ted Unangst wrote:
On 3/30/06, Claus Assmann [EMAIL PROTECTED] wrote:
[does pthread_mutex_destroy() clean up properly if the mutex is
not on the stack?]
it should, unless the mutex is held, in which case it returns EBUSY.
are you checking for that?
I just added an
On Thu, 30 Mar 2006, Claus Assmann wrote:
Is there some simple way to find a memory leak in some OS supplied
library? I have a (constantly running) application that grows in a
week from 5MB to 15MB in size (VSZ and RSS as reported by ps). The
application can be compiled with an optional
On 3/30/06, Claus Assmann [EMAIL PROTECTED] wrote:
Do you have other suggestions of what I should look for?
i mentioned the pthread issue because it's something i know about, but
otherwise, i think you're going to need an instrumented malloc.
On Thursday 30 March 2006 1:25 pm, Claus Assmann wrote:
On Thu, Mar 30, 2006, Ted Unangst wrote:
particular to pthreads, if you are using mutexes or somesuch on the
stack, you will leak memory. (the lock on the stack is just a
pointer, it gets allocated on first use).
All mutexes are
Kurt Miller [EMAIL PROTECTED] and others write:
Date: Thu, 30 Mar 2006 14:01:55 -0500
From: Kurt Miller [EMAIL PROTECTED]
Subject: Re: How to find memory leak in library/OS?
In-reply-to: [EMAIL PROTECTED]
To: Claus Assmann [EMAIL PROTECTED]
Cc: misc@openbsd.org
Reply-to: [EMAIL PROTECTED
17 matches
Mail list logo
