Address Space Summary within gdb?

Address Space Summary within gdb?

[Andreas Borchert]

Hello,

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.

Thanks, Andreas.

-- 
Dr. Andreas F. Borchert, SAI, Universitaet Ulm | Habe Mut, dich deines
Helmholtzstrasse 18, E02, Tel +49 731 50-23572 | eigenen Verstandes zu
http://www.mathematik.uni-ulm.de/sai/borchert/ | bedienen! -- I. Kant

Re: Address Space Summary within gdb?

[Andreas Schwab]

"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.

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."

Re: Address Space Summary within gdb?

[Andreas Borchert]

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.

Andreas.

-- 
Dr. Andreas F. Borchert, SAI, Universitaet Ulm | Habe Mut, dich deines
Helmholtzstrasse 18, E02, Tel +49 731 50-23572 | eigenen Verstandes zu
http://www.mathematik.uni-ulm.de/sai/borchert/ | bedienen! -- I. Kant

Re: Address Space Summary within gdb?

[Andreas Schwab]

"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."