From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: nikos chistou <paravatis92@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: view all the memory allocated to a process ?
Date: Mon, 16 Nov 2009 10:17:00 -0000 [thread overview]
Message-ID: <20091115193514.GA2447@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <26362209.post@talk.nabble.com>
On Sun, 15 Nov 2009 20:12:12 +0100, nikos chistou wrote:
> I want to know if there is a way to view all the memory allocated to
> a process (the regions or the offsets and their protection)
this is offtopic for gdb.
And the standard glibc memory allocator does not provide allocated memory
introspection as it would reduce its performance.
You need to change the default allocator, you track the memory easily
yourself:
info '(libc)Hooks for Malloc'
using some small .so loaded by:
(gdb) set env LD_PRELOAD=./myhook.so
Or rather check some tools like valgrind which may provide such functionality
out of the box (I do not know myself).
Regards,
Jan
prev parent reply other threads:[~2009-11-15 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 8:29 nikos chistou
2009-11-16 10:17 ` Jan Kratochvil [this message]
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=20091115193514.GA2447@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=paravatis92@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