Re: [Valgrind-users] Question :: Massif Tool
The official Massif documentation is at http://valgrind.org/docs/manual/ms-manual.html. time is measured in instructions, not nanoseconds, so as to make runs repeatable. The various _B values are sizes of things in bytes. See the above URL for details. J On 08/04/2019 07:34, Yogi S wrote: > Hi, > i am a novice. when I capture the snapshots using massif tool following are > the attributes seen in the snapshot. > > time=5325473651 > mem_heap_B=232194935 > mem_heap_extra_B=1038185 > mem_stacks_B=0 > heap_tree=peak > > If I understand correctly time would refer to the time in nano seconds (*may > be some other units*) > But what are the mem_heap_B , mem_heap_extra_B and mem_stacks_B and > heap_tree. > > I tried searching for suitable article online on this could not get one. > can you help me with the same? > > Regards > Yogi > > > > ___ > Valgrind-users mailing list > Valgrind-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/valgrind-users > ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
[Valgrind-users] Question :: Massif Tool
Hi, i am a novice. when I capture the snapshots using massif tool following are the attributes seen in the snapshot. time=5325473651 mem_heap_B=232194935 mem_heap_extra_B=1038185 mem_stacks_B=0 heap_tree=peak If I understand correctly time would refer to the time in nano seconds (*may be some other units*) But what are the mem_heap_B , mem_heap_extra_B and mem_stacks_B and heap_tree. I tried searching for suitable article online on this could not get one. can you help me with the same? Regards Yogi ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
Re: [Valgrind-users] [HELP] Android use LD to link the program but the valgrind can not report malloc leak;
Elf file type is DYN (Shared object file) Entry point 0x47000 There are 9 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align PHDR 0x40 0x0040 0x0040 0x0001f8 0x0001f8 R 0x8 LOAD 0x00 0x 0x 0x0469bc 0x0469bc R 0x1000 LOAD 0x047000 0x00047000 0x00047000 0x10ee20 0x10ee20 E 0x1000 LOAD 0x156000 0x00156000 0x00156000 0x00a598 0x221fa8 RW 0x1000 DYNAMIC 0x15ee20 0x0015ee20 0x0015ee20 0x0001c0 0x0001c0 RW 0x8 GNU_RELRO 0x15a000 0x0015a000 0x0015a000 0x006598 0x007000 R 0x1 GNU_EH_FRAME 0x02a2a4 0x0002a2a4 0x0002a2a4 0x005ddc 0x005ddc R 0x4 GNU_STACK 0x00 0x 0x 0x00 0x00 RW 0 NOTE 0x000238 0x0238 0x0238 0x38 0x38 R 0x4 Valgrind can not find memory leak with malloc; Which version of valgrind? (Run "valgrind --version".) Please post the valgrind output just before and just after the place where the report of memory leaks should appear. Please re-run using "valgrind -v ..." and show the output from the very beginning until the last REDIR message, such as: --15470-- REDIR: 0x4ebf390 (libc.so.6:malloc) redirected to 0x4c2edc9 (malloc) --15470-- REDIR: 0x4ebf9e0 (libc.so.6:free) redirected to 0x4c2ffca (free) I think maybe there is something different with GNU LD command; because there is two segment new； Please focus on the text in blue; The text that was originally posted to [valgrind-users] was all in black. There was no blue. Please post the output from: readelf --dynamic ldd ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
[Valgrind-users] [HELP] Android use LD to link the program but the valgrind can not report malloc leak;
Elf file type is DYN (Shared object file) Entry point 0x47000 There are 9 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align PHDR 0x40 0x0040 0x0040 0x0001f8 0x0001f8 R 0x8 LOAD 0x00 0x 0x 0x0469bc 0x0469bc R 0x1000 LOAD 0x047000 0x00047000 0x00047000 0x10ee20 0x10ee20 E 0x1000 LOAD 0x156000 0x00156000 0x00156000 0x00a598 0x221fa8 RW 0x1000 DYNAMIC0x15ee20 0x0015ee20 0x0015ee20 0x0001c0 0x0001c0 RW 0x8 GNU_RELRO 0x15a000 0x0015a000 0x0015a000 0x006598 0x007000 R 0x1 GNU_EH_FRAME 0x02a2a4 0x0002a2a4 0x0002a2a4 0x005ddc 0x005ddc R 0x4 GNU_STACK 0x00 0x 0x 0x00 0x00 RW 0 NOTE 0x000238 0x0238 0x0238 0x38 0x38 R 0x4 Valgrind can not find memory leak with malloc; I think maybe there is something different with GNU LD command; because there is two segment new； Please focus on the text in blue; ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
