Process and tools for investigating memory leaks
edited Jul 30, 2010 1:46AM in Oracle Solaris Performance, Panics, Hangs, and Dtrace (MOSC) 4 commentsAnswered
Hello,
I am attempting to track down a possible memory leak in an application (C++) that runs on Solaris 10 and was looking for pointers on the best way to go about debugging the issue. The current status is:
I am attempting to track down a possible memory leak in an application (C++) that runs on Solaris 10 and was looking for pointers on the best way to go about debugging the issue. The current status is:
- I do not have a concrete scenario that causes the application to use excessive amounts of memory
- I have set a ulimit -d for the user running the application. This
is resulting in the application creating a core at the point it hits
the max data segment.
- Analysis of the stack trace is not providing enough information to pinpoint the reason for the growth
0