This is a tool for Solaris users only, however it is easier to use than Insure and usually more stable. Those running Solaris are recommended to use this over Insure. Hey, even its GUI is more colorful.
First, build the binary in the usual fashion. So you have the binary, now what? Simple, run the command
- workshop (if it isn't in your path, you want to add /opt/SUNWspro/bin/workshop to your path)
from your workdir and watch all the pretty windows pop up. You can close the "about workshop" window and deselect it from being opened ever again by checking the little box. Then go to the "Debug" option under the menu bar, and click on "New Program."
Next navigate through and find your binary, double click on it and a bunch of windows pop up like "opening GNUemacs" and "loading code," don't worry about them. You know that you are ready to start debugging when the emacs window opens. Next click on the
menu option "Checks" and select "Enable Memuse Checking." Then go over to the "Execute" menu option and select "Start." Run your application as usual, but if you have a .tcl file please start by typing "source [Your File].tcl" just remember that the
memory leaks will only be shown after you exit the application. Once your application exits, Workshop will build a report detailing the amount of memory leaked, the fuctions in which you lost the memory and when you click on the blue function links, you
will be taken to the exact new statement which is causing the leak.
please contact me with comments/questions at beylin@SLAC.Stanford.EDU
[Top of the Page] [Babar Home Page] [Memory Leak Page]
|
