Hi, a related question. The following is a snippet from /proc/<pid>/maps 000000000fe76000-000000000fe81000 r-xp 0000000000000000 08:03 8798 /lib/libnss_files.so.2 000000000fe81000-000000000fe86000 ---p 000000000000b000 08:03 8798 /lib/libnss_files.so.2 000000000fe86000-000000000fe91000 rwxp 0000000000000000 08:03 8798 /lib/libnss_files.so.2 000000000fea1000-000000000ffbb000 r-xp 0000000000000000 08:03 8787 /lib/libc.so.6 000000000ffbb000-000000000ffc1000 ---p 000000000011a000 08:03 8787 /lib/libc.so.6 000000000ffc1000-000000000ffea000 rwxp 0000000000110000 08:03 8787 /lib/libc.so.6 Just out of curiousity. When the permission of the vm_area_struct is "r-xp", it's probably the code section. When the permission is "rwxp", it's most likely to be the data section. What does it mean when a vm_area is "---p"? It doesn't make much sense to me. Why would you want to generate a page fault everytime this range of memory is accesses? Btw, this snippet is from a PPC machine. On x86, you don't see this kind of behavior. Any ideas/speculations? Thanks. - Hai On Wed, 30 Jul 2003, Rik van Riel wrote: > On Sat, 26 Jul 2003, Anticipating a Reply wrote: > > > How to find out how much of the total > > Virtual memory ( i.e. 4GB for IA-32 ) > > is being used & how much is free > > Every process has its own virtual memory area. You can check > this area in /proc/<pid>/maps as well as /proc/<pid>/status. > > Rik > -- > "Debugging is twice as hard as writing the code in the first place. > Therefore, if you write the code as cleverly as possible, you are, > by definition, not smart enough to debug it." - Brian W. Kernighan > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ > > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
