From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "", Issuer "NORTEL" (not verified)) by ozlabs.org (Postfix) with ESMTPS id 31B4BDDD1C for ; Thu, 26 Mar 2009 07:10:14 +1100 (EST) Message-ID: <49CA8501.1000000@nortel.com> Date: Wed, 25 Mar 2009 13:24:49 -0600 From: "Chris Friesen" MIME-Version: 1.0 To: linuxppc-dev@ozlabs.org, linux-kernel-owner@vger.kernel.org Subject: /proc//maps offset output broken Content-Type: text/plain; charset=ISO-8859-1; format=flowed List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , I was validating some code dealing with /proc//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