Hey
I just wanted to know what programs any of you have used to track down a
memory leak in your programs?
Also wondering if there is maybe a good tutorial on the subject under
FreeBSD or even linux if possible.
Im running FreeBSD 4.9 so just looking for something try to help me track it
down.
Cole wrote:
Hey
I just wanted to know what programs any of you have used to track down a
memory leak in your programs?
Also wondering if there is maybe a good tutorial on the subject under
FreeBSD or even linux if possible.
Im running FreeBSD 4.9 so just looking for something try to help me track
Hi
Ok this is just a more direct question that the thread Memory Leak.
I have a program using pthread_create, and it runs fine, no compile errors
or warnings, it all works fine, not a single issue, but it very very slowly
uses up memory. The program creates a fixed number of threads, and after
I just wanted to know what programs any of you have used to track down a
memory leak in your programs?
this reminds me of something... :-/
I created a port for Doug Rabson's FreeBSD port[1] of valgrind [2]. He
considered my work ready for the ports tree, but he also said that that
he doesn't
On Sat, May 22, 2004 at 11:52:19AM -0700 I heard the voice of
Tim Kientzle, and lo! it spake thus:
The one problem I've had is that dmalloc.h redefines some standard
functions, which can cause gcc to complain.
I usually just have a flag in my Makefile to enable dmalloc (adding a
-D to the cc
On Sat, 22 May 2004, Cole wrote:
Hi
Ok this is just a more direct question that the thread Memory Leak.
I have a program using pthread_create, and it runs fine, no compile errors
or warnings, it all works fine, not a single issue, but it very very slowly
uses up memory. The program
On Saturday 22 May 2004 10:39 pm, Cole wrote:
Hi
Ok this is just a more direct question that the thread Memory Leak.
I have a program using pthread_create, and it runs fine, no compile errors
or warnings, it all works fine, not a single issue, but it very very slowly
uses up memory. The
Hi!
I've written an rc.d script that can start/stop/restart jails, if they
follow a certain pattern of setup. I'm strongly considering the
placement of this in ports or base (ports seems most appropriate).
Basically, if you have jails in /usr/local/var/jail/IP, my script can
start it up
Very odd, my jails.sh script was not allowed to pass or something. So,
I'm pasting it into this email.
#!/bin/sh
#
# Start the jails at boot-up.
# The only jails it can start properly are the ones in directories labelled
# with an IP address.
JAILBASE=/usr/local/var/jail
LS=/bin/ls
In message: [EMAIL PROTECTED]
Tim Kientzle [EMAIL PROTECTED] writes:
: Cole wrote:
: Hey
:
: I just wanted to know what programs any of you have used to track down a
: memory leak in your programs?
: Also wondering if there is maybe a good tutorial on the subject under
: FreeBSD
If anyone testing the bge changes needs access to a pair of machines that
are linked back to back via bge's, I can provide it - root and all - for
testing. I'm currently testing -CURRENT on a pair of Poweredge 2650's
that aren't in production yet and would be willing to let them be used for
the
11 matches
Mail list logo