From: Balazs Scheidler <bazsi@balabit.hu>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: printing mapped memory regions
Date: Mon, 02 Jul 2007 16:55:00 -0000 [thread overview]
Message-ID: <1183395311.31266.33.camel@bzorp.balabit> (raw)
In-Reply-To: <20070702164705.GA19981@caradoc.them.org>
On Mon, 2007-07-02 at 12:47 -0400, Daniel Jacobowitz wrote:
> On Mon, Jul 02, 2007 at 06:44:59PM +0200, Balazs Scheidler wrote:
> > Hi,
> >
> > Is it possible to query the list of mapped virtual memory regions of a
> > running process/core file using gdb?
>
> No, not yet.
>
> > I would like something similar to what /proc/<pid>/maps file provides on
> > Linux, but unluckily that information is not available (grsec zeroes
> > those values so nothing to find there).
>
> If there were, GDB would read /proc/<pid>/maps to implement it.
Hmm.. any other way? The core file supposedly contains all of this
information doesn't it?
--
Bazsi
next prev parent reply other threads:[~2007-07-02 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 16:45 Balazs Scheidler
2007-07-02 16:47 ` Daniel Jacobowitz
2007-07-02 16:55 ` Balazs Scheidler [this message]
2007-07-02 17:04 ` Daniel Jacobowitz
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=1183395311.31266.33.camel@bzorp.balabit \
--to=bazsi@balabit.hu \
--cc=drow@false.org \
--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