git-hulk / gperftools

Automatically exported from code.google.com/p/gperftools
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

heap-profile can not get stack info ? #330

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. insert HeapProfilerStart(), HeapProfilerStop() and HeapProfilerDump() in 
proper place in my code and build my binary with libtcmalloc_and_profiler.a
2. start my binary with HEAP_PROFILE_ALLOCATION_INTERVAL and 
HEAP_PROFILE_INUSE_INTERVAL set huge enough to prevent it dumping files from 
time to time (so my binary dumps heap profile only when HeapProfilerDump is 
being called)
3. wait util heap profile dumped
4. use pprof transfer the heap profile to a gif file

What is the expected output? What do you see instead?
I expected to see the stack back tracing information in the gif file.
But in the gif file, most of the nodes is the child node, only only few nodes 
can trace its father node.

What version of the product are you using? On what operating system?
libtcmalloc.a version: 1.6 release
libunwind.a version: 0.99
OS: Red Hat Enterprise Linux AS release 4 x86_64

Please provide any additional information below.
The heap profile and gif file attached.
Pls take a look if needed.

Original issue reported on code.google.com by qifa.z...@gmail.com on 28 Apr 2011 at 7:05

Attachments:

GoogleCodeExporter commented 9 years ago
It looks like it's unable to get good stack traces for some reason.  Perhaps a 
more recent version of libunwind, from the libunwind website, would help?  Or 
you could try building perftools with --enable-frame-pointer and build your 
binary with frame pointers, if you can.

Original comment by csilv...@gmail.com on 28 Apr 2011 at 9:48

GoogleCodeExporter commented 9 years ago
problem solved by rebuilding libunwind and google perftools without the 
--enable-frame-pointer=yes option

Thank you for replying:-)

Original comment by qifa.z...@gmail.com on 5 May 2011 at 11:50

GoogleCodeExporter commented 9 years ago

Original comment by csilv...@gmail.com on 18 Oct 2011 at 5:48