From: Andreas Schwab <schwab@suse.de>
To: "Andreas Borchert" <borchert@mathematik.uni-ulm.de>
Cc: gdb@sources.redhat.com
Subject: Re: Address Space Summary within gdb?
Date: Fri, 11 Jun 2004 11:37:00 -0000 [thread overview]
Message-ID: <jehdtixr50.fsf@sykes.suse.de> (raw)
In-Reply-To: <20040611113028.26796.qmail@thales.mathematik.uni-ulm.de> (Andreas Borchert's message of "Fri, 11 Jun 2004 13:30:28 +0200")
"Andreas Borchert" <borchert@mathematik.uni-ulm.de> writes:
> On Fri, Jun 11, 2004 at 12:13:57PM +0200, Andreas Schwab wrote:
>> "Andreas Borchert" <borchert@mathematik.uni-ulm.de> writes:
>>
>> > I am looking for a gdb command that provides a summary about the virtual
>> > address space of the process being debugged. Unfortunately, I was unable
>> > to find anything in the documentation.
>> >
>> > I am hoping for something similar to the output of pmap(1) or something
>> > equivalent to the ``$m'' command of adb.
>>
>> (gdb) help info proc
>> Show /proc process information about any running process.
>> Specify any process id, or use the program being debugged by default.
>> Specify any of the following keywords for detailed info:
>> mappings -- list of mapped memory regions.
>> stat -- list a bunch of random process info.
>> status -- list a different bunch of random process info.
>> all -- list all available /proc info.
>
> Thanks. However, these commands are not supported for no longer
> running processes, i.e. if just a core is left.
Try info target.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2004-06-11 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 9:56 Andreas Borchert
2004-06-11 10:14 ` Andreas Schwab
2004-06-11 11:30 ` Andreas Borchert
2004-06-11 11:37 ` Andreas Schwab [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=jehdtixr50.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=borchert@mathematik.uni-ulm.de \
--cc=gdb@sources.redhat.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