From: santoshp <santosh.pradhan@gmail.com>
To: 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 17:18:00 -0000 [thread overview]
Message-ID: <33897108.post@talk.nabble.com> (raw)
In-Reply-To: <87pq9v9bht.fsf@fleche.redhat.com>
The application is a C++ application running on Linux (RHEL 5.7 x86_64). It
uses a private memory allocator (variation of ptmalloc). The gdb-heap link
says it works for python objects and work for c++ is under process. Can I
use the gdb-heap ?
Thanks,
Santosh
Nothing built in, but there is gdb-heap, if you're on a system using
glibc.
https://fedorahosted.org/gdb-heap/
Tom
--
View this message in context: http://old.nabble.com/Is-there-any-mechanism-in-GDB-to-print-memory-allocation-pattern-in-a-core-dump-file-tp33895291p33897108.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next prev parent reply other threads:[~2012-05-23 17:18 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
2012-05-23 17:18 ` santoshp [this message]
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=33897108.post@talk.nabble.com \
--to=santosh.pradhan@gmail.com \
--cc=gdb@sourceware.org \
/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