Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 80382 invoked from network); 3 Jun 2008 09:04:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Jun 2008 09:04:03 -0000 Received: (qmail 76485 invoked by uid 500); 3 Jun 2008 09:04:00 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 76470 invoked by uid 500); 3 Jun 2008 09:04:00 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 76458 invoked by uid 99); 3 Jun 2008 09:04:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jun 2008 02:04:00 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of torsten.foertsch@gmx.net designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 03 Jun 2008 09:03:04 +0000 Received: (qmail invoked by alias); 03 Jun 2008 09:03:26 -0000 Received: from p57A5F7F2.dip.t-dialin.net (EHLO opi.home) [87.165.247.242] by mail.gmx.net (mp002) with SMTP; 03 Jun 2008 11:03:26 +0200 X-Authenticated: #1700068 X-Provags-ID: V01U2FsdGVkX1+8+s981XS8xqqa8+rRGBG8EF0/YjQXvZCNxQt4EH Cw9MYtC2RB5DJ+ From: Torsten Foertsch To: modperl@perl.apache.org, Perl Porters Subject: Linux::Smaps kernel/perlio dependencies Date: Tue, 3 Jun 2008 11:04:00 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806031104.01044.torsten.foertsch@gmx.net> X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org Hi, I have recently got a bug report about Linux::Smaps. The poster said it'd report 2 [vdso] areas and that it can be cured if /proc/self/smaps is opened with '<:stdio'. Later on he also found the behavior depends on the kernel version, 2.6.25.3 shows 2 vdsos 2.6.23.1-21 only one. Since I don't have any of these kernels I am asking for help. To all of my knowledge multiple vdsos is nonsense. But is it a kernel bug or a bug in the perlio layer? Could you please run the following command on various combinations of linux kernel and perlio? PERLIO="stdio" perl -pe 'BEGIN {my $smaps="/proc/$$/smaps"; open STDIN, "<", $smaps or die "$!\n"; system "cat -n $smaps"} $_="$.\t$_"' | grep vdso It should print 2 almost identical lines. If there are more please report. Here an example: $ PERLIO="stdio" perl -pe 'BEGIN {my $smaps="/proc/$$/smaps"; open STDIN, "<", $smaps or die "$!\n"; system "cat -n $smaps"} $_="$.\t$_"'|grep vdso 321 ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso] 321 ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso] Keep in mind that /proc/$$/smaps exists only for kernels >=2.6.14. Thanks, Torsten