From: xgsa <xgsa@yandex.ru>
To: Hei Chan <structurechart@yahoo.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Memory Dump
Date: Thu, 03 May 2012 06:56:00 -0000 [thread overview]
Message-ID: <4FA22BFD.1060600@yandex.ru> (raw)
In-Reply-To: <1335710405.38804.YahooMailNeo@web162403.mail.bf1.yahoo.com>
Hi,
I am not sure, but it seems massif (the tool from the valgrind
toolchain) could help you.
P.S. However the question is still interesting - is there a possibility
to solve the problem with gdb? Could someone answer it?
Anton.
-------- Original message --------
>
> Hi,
>
> I wonder whether it is possible to dump all the objects created in the memory at the moment with GDB (I am on v7.0.1).
>
> What I am trying to achieve is to identify which types of objects take up most of the memory at the moment.
>
> Valgrind doesn't catch it and so I believe that it is some logical bug in my code that keeps creating the objects and free all of them at the end (i.e. program terminated).
>
> Thanks in advance.
>
>
> Cheers,
> Hei
>
>
next prev parent reply other threads:[~2012-05-03 6:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 14:40 Hei Chan
2012-05-03 6:56 ` xgsa [this message]
2012-05-03 14:17 ` Aurelian Melinte
2012-05-03 19:23 ` Philippe Waroquiers
2012-05-06 0:55 ` Hei Chan
2012-05-06 7:49 ` Philippe Waroquiers
2012-05-06 0:43 ` Hei Chan
2012-05-09 20:25 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FA22BFD.1060600@yandex.ru \
--to=xgsa@yandex.ru \
--cc=gdb@sourceware.org \
--cc=structurechart@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).