From: Tom Tromey <tromey@redhat.com>
To: santoshp <santosh.pradhan@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Is there any mechanism in GDB to print memory allocation pattern in a core dump file
Date: Wed, 23 May 2012 15:13:00 -0000 [thread overview]
Message-ID: <87pq9v9bht.fsf@fleche.redhat.com> (raw)
In-Reply-To: <33895291.post@talk.nabble.com> (santoshp's message of "Wed, 23 May 2012 05:32:57 -0700 (PDT)")
>>>>> "Santosh" == santoshp <santosh.pradhan@gmail.com> writes:
Santosh> I got a crash for which the size of the core file is little
Santosh> bigger i.e. ~9GB. Initial impression is that there might be
Santosh> some memory leaks in the process as the size is bugger than the
Santosh> usual size. Is there any mechanism in GDB/Linux I can find out
Santosh> the memory allocation pattern in the core file? e.g. There is
Santosh> a tool debug diag in Windows which can do this nicely from dump
Santosh> file.
Nothing built in, but there is gdb-heap, if you're on a system using
glibc.
https://fedorahosted.org/gdb-heap/
Tom
next prev parent reply other threads:[~2012-05-23 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 12:33 santoshp
2012-05-23 15:13 ` Tom Tromey [this message]
2012-05-23 17:18 ` santoshp
2012-05-25 14:27 ` 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=87pq9v9bht.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=santosh.pradhan@gmail.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