From: "Chris Friesen" <cfriesen@nortel.com>
To: linuxppc-dev@ozlabs.org, linux-kernel-owner@vger.kernel.org
Subject: /proc/<pid>/maps offset output broken
Date: Wed, 25 Mar 2009 13:24:49 -0600 [thread overview]
Message-ID: <49CA8501.1000000@nortel.com> (raw)
I was validating some code dealing with /proc/<pid>/maps on 2.6.29 and
was surprised when it failed. It turns out that at least on my ppc64 G5
machine the offset value for the last entry is strange--it shows up as a
64-bit value even though the process itself is only 32-bit.
This behaviour also shows up in 2.6.25, but doesn't in 2.6.14. I
haven't yet tested anything else in between.
[cfriesen@localhost cfriesen]$ cat /proc/self/maps
00100000-00103000 r-xp 00100000 00:00 0 [vdso]
0fe70000-0ffbf000 r-xp 00000000 08:03 4312393 /lib/tls/libc-2.3.3.so
0ffbf000-0ffc0000 ---p 0014f000 08:03 4312393 /lib/tls/libc-2.3.3.so
0ffc0000-0ffc2000 r--p 00150000 08:03 4312393 /lib/tls/libc-2.3.3.so
0ffc2000-0ffc6000 rwxp 00152000 08:03 4312393 /lib/tls/libc-2.3.3.so
0ffc6000-0ffc8000 rwxp 0ffc6000 00:00 0
0ffd0000-0ffec000 r-xp 00000000 08:03 4309011 /lib/ld-2.3.3.so
0fff0000-0fff1000 r--p 00020000 08:03 4309011 /lib/ld-2.3.3.so
0fff1000-0fff2000 rwxp 00021000 08:03 4309011 /lib/ld-2.3.3.so
10000000-10004000 r-xp 00000000 08:03 917536 /bin/cat
10013000-10015000 rwxp 00003000 08:03 917536 /bin/cat
10015000-10036000 rwxp 10015000 00:00 0 [heap]
f7deb000-f7feb000 r--p 00000000 08:03 2560322
/usr/lib/locale/locale-archive
f7feb000-f7fec000 rw-p f7feb000 00:00 0
ffe6d000-ffe82000 rw-p ffffffeb000 00:00 0 [stack]
I'm at a loss to explain what's going on here. Anyone got any ideas?
Thanks,
Chris
next reply other threads:[~2009-03-25 20:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 19:24 Chris Friesen [this message]
2009-04-01 23:18 ` Resend: /proc/<pid>/maps offset output broken in 2.6.29 Chris Friesen
2009-04-02 8:04 ` Michael Ellerman
2009-04-02 12:43 ` Hugh Dickins
2009-04-02 17:53 ` Chris Friesen
2009-04-02 19:10 ` Hugh Dickins
2009-04-02 20:45 ` Chris Friesen
2009-04-05 18:51 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49CA8501.1000000@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).