2009-07-14 08:41:37     content of /proc/pid/maps

Document created by Aaronwu Employee on Aug 16, 2013
Version 1Show Document
  • View in full screen mode

2009-07-14 08:41:37     content of /proc/pid/maps

victor nikonov (BELARUS)

Message: 77217   

 

Hi. If we have the standart app :

 

# ps

  PID Uid VSZ Stat Command

  ...

  197 root 496 S /bin/watchdogd -f -s -w 5 -k

 

  ...

 

 

# cat /proc/197/status

Name: watchdogd

State: S (sleeping)

...

Mem: 196128 bytes

Slack: 12288 bytes

Shared: 360736 bytes

Threads: 1

...

 

 

# cat /proc/197/maps

00380000-003bd000 r-xs 00000000 00:01 99 /lib/libuClibc-0.9.29.so

003c0000-003cb000 r-xs 00000000 00:01 65 /lib/libgcc_s.so.1

003d0000-003d8000 r-xs 00000000 00:01 64 /lib/ld-uClibc-0.9.29.so

0197a000-0197b000 rw-p 00000000 00:00 0

0197b000-0197c000 rw-p 00001000 00:01 172 /bin/watchdogd (deleted)

0197c000-0197e000 r-xs 00000000 00:01 172 /bin/watchdogd (deleted)

01a49000-01a4a000 rw-p 00007000 00:01 64 /lib/ld-uClibc-0.9.29.so

01a4c000-01a4e000 rw-p 00000000 00:00 0

01a50000-01a55000 rw-p 00000000 00:00 0

01a60000-01a80000 rwxp 00000000 00:00 0

 

 

As I understand - 01a60000-01a80000 rwxp 00000000 00:00 0 - it's area for stack(128k by default)

 

What for others  private areas with inode==0?

 

Best Regards

 

Victor Nikonov

QuoteReplyEditDelete

 

 

2009-07-14 08:45:23     Re: content of /proc/pid/maps

Mike Frysinger (UNITED STATES)

Message: 77218   

 

at least one is for the heap, and probably another is for the .data/.bss

 

look at the ELF PHDRs from the watchdog binary

Attachments

    Outcomes