pmap question
000100007968K r-x-- /export/home/home0/corems_V0.2.2.0/TEST/DMNG/ElementManager_cm100
Hi,
I would like to understand the information returned by the pmap tool, and more precisely how can I get more details about the source of such heap (65Mb). Is there any way to understand what library is allocating this data ?
Following the first part of the pmap result:
007E6000248K rwx-- /export/home/home0/corems_V0.2.2.0/TEST/DMNG/ElementManager_cm100
008240003952K rwx--[ heap ]
00C0000065536K rwx--[ heap ]
F77BA00024K rwx-R[ stack tid=28 ]
F78080008K rwx-R[ anon ]
F780C00016K rwx-R[ stack tid=27 ]
F785E0008K rwx-R[ stack tid=26 ]
F78AE0008K rwx-R[ stack tid=25 ]
F78FC00016K rwx-R[ stack tid=24 ]
F794E0008K rwx-R[ stack tid=23 ]
F79EC00016K rwx-R[ stack tid=21 ]
.....
Thanks.
Regards.
Yaakov Berkovitch
[916 byte] By [
yakovyu] at [2007-11-26 11:56:31]
# 2
If you want to know where in the program memory is being allocated, you can run it under dbx and trap calls to malloc, calloc, and realloc. (The default versions of operator new in Sun C++ just call malloc, so you don't need to trap calls to all the versions of operator new.)
If you are concerned about possibly incorrect usage of the heap, you can enable Run-Time Checking under dbx, using the dbx command
check -all
The checking is more complete on SPARC, but some information is available on x86 and x64 platforms.
For a more detailed picture, use the Performance Analyzer that comes with Sun Studio.
# 3
Thans for you responses.
I will try the solution you propose using dbx to catch the malloc.
I was surprised of a so big heap because this size is reached just after my process terminated its loading. Our application is not allocating a so big amount of memory when the process is initializing, so I want to understand what library the process is linked to impact the heap.
Thanks.
Regards.
Yaakov.
