10-17-2002
ps -elf will show you the memory usage of processes on your system. You can run ps -elf every so often and compare the size of the processes between runs. If you see one getting larger, it is using more memory. If it continues to use more and more memory or stops doing any actual work and does not free up memory, you may have a leak. I say 'may' because some code will keep the pool of memory allocated to it and use it when it starts processing again.
10 More Discussions You Might Find Interesting
1. HP-UX
Hi folks,
We are using following listed configurations for a particular application.
HP-UX 11i
Sun Java 2 SDK Standard Edition 1.4.1 (version shipped with WebLogic 8)
Oracle 9i Release 2 (Oracle 9.2.0)
BEA WebLogic Server 8.1 SP3
It seems a memory leak when we use above configurations.... (1 Reply)
Discussion started by: gimhan90
1 Replies
2. Programming
hi, i am a c++ programmer working on linux(redhat linux8.0) environment, i need to find out the memory leaks, so far i didn't used any tools, so what are the tools are available, and whic one is good to use. plz provide with a small example. (1 Reply)
Discussion started by: sarwan
1 Replies
3. UNIX for Advanced & Expert Users
Hi Unix lovers,
I am facing a strange problem about memory leak. One component of our product show memory leak at customer's end but not in development environment. The memory used by the exe goes on increasing at customer end but not in dev.
customer has same m/c(HP unix 11i) , the same... (1 Reply)
Discussion started by: shriashishpatil
1 Replies
4. Shell Programming and Scripting
Hi all,
Has anyone out there a shell script to detect memory leaks on unix machines?
And if so what way did they go about it .? (5 Replies)
Discussion started by: nano2
5 Replies
5. UNIX and Linux Applications
Hello all
Is there good free ware tools to check software memory leaks ?
Some thing like purify
on unix platforms sun/hp/linux
Thanks (3 Replies)
Discussion started by: umen
3 Replies
6. Solaris
Hi,
Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:-
1. Total Physical Memory in the system(total RAM).
2. Available Physical Memory(i.e. RAM Usage)
3. Total (Logical) Memory in the system
4. Available (Logical) Memory.
I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies
7. AIX
Hi all,
I have written a small code just to invoke main and return immediately. When built with libpthread on AIX box, valgrind throws lots of memory leak errors. But when built without libpthread, no issues at all.
Here is the sample run for your look. Any idea where I might be going wrong?... (3 Replies)
Discussion started by: visionofarun
3 Replies
8. Emergency UNIX and Linux Support
Hello!
I've been struggling for not few hours with memory leaks on this
machine. I'm running linux 2.6.32-5-686, and the problem is as follows:
Some months ago, I have compiled kernel 2.6.33-2-686 without any issues
in this same machine. This week I have tried compiling GNUzilla Icecat
and... (23 Replies)
Discussion started by: teresaejunior
23 Replies
9. Solaris
Hi Experts,
Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing.
Why memory utilization on solaris always looks high?
I have statement about memory on solaris, is this true:
Memory in solaris is used for... (4 Replies)
Discussion started by: edydsuranta
4 Replies
10. Programming
Suppose I have a main() function with only one malloc statement allocating say some 1 gb memory. Also say my system has 1 gb of ram.
main()
{
malloc(1gb)
return(0)
}
The program above exits without freeing the memory.
In this case will the 1 gb of heap memory be returned... (9 Replies)
Discussion started by: rupeshkp728
9 Replies
LEARN ABOUT FREEBSD
elf64_checksum
GELF_CHECKSUM(3) BSD Library Functions Manual GELF_CHECKSUM(3)
NAME
elf32_checksum, elf64_checksum, gelf_checksum -- return the checksum of an ELF object
LIBRARY
ELF Access Library (libelf, -lelf)
SYNOPSIS
#include <libelf.h>
long
elf32_checksum(Elf *elf);
long
elf64_checksum(Elf *elf);
#include <gelf.h>
long
gelf_checksum(Elf *elf);
DESCRIPTION
These functions return a simple checksum of the ELF object described by their argument elf. The checksum is computed in way that allows its
value to remain unchanged in presence of modifications to the ELF object by utilities like strip(1).
Function elf32_checksum() returns a checksum for an ELF descriptor elf of class ELFCLASS32.
Function elf64_checksum() returns a checksum for an ELF descriptor elf of class ELFCLASS64.
Function gelf_checksum() provides a class-independent way retrieving the checksum for ELF object elf.
RETURN VALUES
These functions return the checksum of the ELF object, or zero in case an error was encountered.
ERRORS
These functions may fail with the following errors:
[ELF_E_ARGUMENT] Argument elf was NULL.
[ELF_E_ARGUMENT] Argument elf was not a descriptor for an ELF file.
[ELF_E_ARGUMENT] The ELF descriptor elf was not opened for reading or updating.
[ELF_E_CLASS] For functions elf32_checksum() and elf64_checksum(), ELF descriptor elf did not match the class of the called function.
[ELF_E_HEADER] The ELF object specified by argument elf had a malformed executable header.
[ELF_E_RESOURCE] An out of memory condition was detected during processing.
[ELF_E_SECTION] The ELF object specified by argument elf contained a section with a malformed section header.
[ELF_E_VERSION] The ELF object was of an unsupported version.
SEE ALSO
strip(1), elf(3), gelf(3)
BSD
August 29, 2006 BSD