|
From: Maxim O. <max...@gm...> - 2006-12-07 09:55:12
|
It gives: # cat /proc/self/maps 08048000-0804c000 r-xp 00000000 62:00 17 /bin/cat 0804c000-0804d000 rw-p 00003000 62:00 17 /bin/cat 0804d000-0806e000 rw-p 0804d000 00:00 0 [heap] 40000000-40015000 r-xp 00000000 62:00 3667 /lib/ld-2.3.3.so 40016000-40017000 r--p 00015000 62:00 3667 /lib/ld-2.3.3.so 40017000-40018000 rw-p 00016000 62:00 3667 /lib/ld-2.3.3.so 40018000-40120000 r-xp 00000000 62:00 3676 /lib/libc-2.3.3.so 40120000-40126000 r--p 00107000 62:00 3676 /lib/libc-2.3.3.so 40126000-40128000 rw-p 0010d000 62:00 3676 /lib/libc-2.3.3.so 40128000-4012a000 rw-p 40128000 00:00 0 bfadb000-bfaf0000 rw-p bfadb000 00:00 0 [stack] 00000000-00000000 ---p 00000000 00:00 0 [vdso] On 12/7/06, Igmar Palsenberg <mai...@jd...> wrote: > > > --402:2:aspacem Reading /proc/self/maps > > --402:2:aspacem <<< SHOW_SEGMENTS: With contents of /proc/self/maps > > (1 segments, 1 segnames) > > --402:2:aspacem 0: ANON 0000000000-00FFFFFFFF 0 ----- > > --402:2:aspacem >>> > > Strange, never seen this before. Does a cat /proc/self/maps in bash give > the same ? > > > > Igmar > |