Torsten,
many thanks for the time taken for the explanation.
I still understand only slightly less than 50% of it, but then I don't
really need to understand more either. I am just very glad and thankful
that there are people such as you who apparently do understand it, upon
which we can rel
On Tue 03 Jun 2008, André Warnier wrote:
> I find it interesting that the answers are all different on system (1),
> but all the same on system (2).
> I don't have a clue as to what it means, or what it does to my systems,
> but I trust you do.
Just to enlighten you. Originally linux on x86 used t
Torsten Foertsch wrote:
On Tue 03 Jun 2008, Torsten Foertsch wrote:
[...]
Thanks to all so far. But could you please try that command for PERLIO=perlio
and perhaps PERLIO=unix too?
Here you go.
I find it interesting that the answers are all different on system (1),
but all the same on sy
Torsten Foertsch wrote:
> It should print 2 almost identical lines. If there are more please report.
Perl 5.8.8 and Linux 2.6.20 only prints 2.
--
Michael Peters
Plus Three, LP
On Tue 03 Jun 2008, Torsten Foertsch wrote:
> 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 v
Hi.
I don't have a clue what this relates to, but just in case it helps for
your sample, here are the outputs for 2 Linux Debian systems (don't know
how to output the version of perlio though) :
1)
[EMAIL PROTECTED]:~# uname -a
Linux arthur 2.6.18-6-686 #1 SMP Thu May 8 07:34:27 UTC 2008 i686
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
