Messages in this thread | | | Date | Tue, 1 Nov 2005 01:13:10 -0400 | From | Albert Cahalan <> | Subject | /proc/*/smaps |
| |
Take a look at those files, trying not to crack up laughing at the file format. Maybe you will cry. Imagine that some apps try to parse those... all of them, repeatedly, while being tolerant of unspecified future changes.
(remember that a filename may have a colon, new fields may be added, new lines may differ in unknown ways, etc.)
Could we fix this ASAP? How about just commenting it out right now, so nothing important starts to rely on it. CONFIG_EXPERIMENTAL would do I guess.
I'll gladly do something sane, but not tonight. I'm sorry I did not catch this earlier; I've been rather sick and I never imagined that this thing would get accepted without a major rework of the file format.
-------- unbelievable example follows --------
08048000-080dc000 r-xp /bin/bash Size: 592 KB Rss: 500 KB Shared_Clean: 500 KB Shared_Dirty: 0 KB Private_Clean: 0 KB Private_Dirty: 0 KB 080dc000-080e2000 rw-p /bin/bash Size: 24 KB Rss: 24 KB Shared_Clean: 0 KB Shared_Dirty: 0 KB Private_Clean: 0 KB Private_Dirty: 24 KB 080e2000-08116000 rw-p Size: 208 KB Rss: 208 KB Shared_Clean: 0 KB Shared_Dirty: 0 KB Private_Clean: 0 KB Private_Dirty: 208 KB b7e2b000-b7e34000 r-xp /lib/tls/libnss_files-2.3.2.so Size: 36 KB Rss: 12 KB Shared_Clean: 12 KB Shared_Dirty: 0 KB Private_Clean: 0 KB Private_Dirty: 0 KB ... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |