01-03-2008
Here are a few C/C++ related memory leak tools to investigate:
mpatrol
njamd
fortify
electric fence
dmalloc
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi!! Experts,
Any ideas how to check for the memory leaks in a process during performance testing?? I dont use purify.. Any way of finding it out using default S/W in HP UX-11
Can U gimme pointers to site having good scripts/tutorials on performance testing??
Thanx in Advance..
:) (3 Replies)
Discussion started by: jyotipg
3 Replies
2. 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
3. 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
4. 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
5. 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
6. AIX
If somebody knows there are some tools can show how many CPU, memory useage on AIX and can automatically send email?
Such as when setup if CPU is used over 80%, send alert by email automatically.
Maybe BMC has this tool? (6 Replies)
Discussion started by: rainbow_bean
6 Replies
7. Solaris
Is there any freeware or shareware which can execute .exe files in solaris 10
if it is please give the link (4 Replies)
Discussion started by: tiwsaj
4 Replies
8. 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
9. 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
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 DEBIAN
fence_node
FENCE_NODE(8) cluster FENCE_NODE(8)
NAME
fence_node - a utility to run fence agents
SYNOPSIS
fence_node [OPTIONS] nodename
DESCRIPTION
This utility runs a fence agent against nodename. The agent and args are taken from the running cluster configuration based on clus-
ter.conf(5).
fence_node is a wrapper around the libfence functions: fence_node() and unfence_node(). These libfence functions use libccs to read the
node fencing configuration, which means that corosync (with cman and ccs) must be running to use fence_node(8).
The fenced(8) daemon is the main user of libfence:fence_node(), and the configuration details for that function are given in the fenced(8)
man page.
Fencing vs. Unfencing
The main use for unfencing is with storage/SAN (non-power) agents.
When using power-based fencing agents, the fencing action itself is supposed to turn a node back on after first turning the power off (this
happens automatically with a "reboot" action, and needs to be configured explicitly as "off" + "on" otherwise.)
When using storage-based fencing agents, the fencing action is not allowed to re-enable a node after disabling it. Re-enabling a fenced
node is only safe once the node has been rebooted. A natural way to re-enable a fenced node's access to storage, is for that node to re-
enable the access itself during its startup process. The cman init script calls fence_node -U (nodename defaults to local nodename when
unfencing). Unfencing a node without an <unfence> configuration (see below) is a no-op.
The basic differences between fencing and unfencing:
Fencing
1. libfence: fence_node(), command line: fence_node nodename
2. Turns off or disables a node.
3. Agents run with the default action of "off", "disable" or "reboot".
4. Performed by a cluster node against another node that fails (by the fenced daemon).
Unfencing
1. libfence: unfence_node(), command line: fence_node -U nodename
2. Turns on or enables a node.
3. Agents run with the explicit action of "on" or "enable".
4. Performed by a cluster node "against" itself during startup (by the cman init script).
OPTIONS
-U Unfence the node, default local node name.
-v Show fence agent results, -vv to also show agent args.
-h Print a help message describing available options, then exit.
-V Print program version information, then exit.
FILES
The Unfencing/unfence_node() configuration is very similar to the Fencing/fence_node() configuration shown in fenced(8). Unfencing is only
performed for a node with an <unfence> section:
<clusternode name="node1" nodeid="1">
<fence>
</fence>
<unfence>
</unfence>
</clusternode>
The <unfence> section does not contain <method> sections like the <fence> section does. It contains <device> references directly, which
mirror the corresponding device sections for <fence>, with the notable addition of the explicit action of "on" or "enable". The same
<fencedevice> is referenced by both fence and unfence <device> lines, and the same per-node args should be repeated.
<clusternode name="node1" nodeid="1">
<fence>
<method name="1">
<device name="myswitch" foo="x"/>
</method>
</fence>
<unfence>
<device name="myswitch" foo="x" action="on"/>
</unfence>
</clusternode>
SEE ALSO
fenced(8)
cluster 2009-12-21 FENCE_NODE(8)