Hi Ken-
I am unable to generate the error with PDL-2.007
either. My system has 8GiB of memory and the
PDL build is using the 64bit index support.
What are the specs of your linux box and could
you please send the output of the 'perldl -V'
command. If you built PDL from sources, then
the build
I couldn't reproduce the problem if I disable the
64bit index support either. Perhaps the problem
is in the perl version. Maybe someone will be
able to reproduce the problem when you have
a specific test case---including me.
--Chris
On Fri, Nov 21, 2014 at 9:34 AM, Chris Marshall
Chris
I didn't know perldl was on my system! It got squirreled away in the perl
directory, outside my path. I found it with locate. Here's the output:
Summary of my PDL configuration
VERSION: PDL v2.007 (supports bad values)
$%PDL::Config = {
'BADVAL_PER_PDL' = '0',
Ken-
You should also have pdl2 on your system as
well. If you have the needed prerequisite module
Devel::REPL installed, then you pdl2 will give you
the new PDL shell, otherwise, it falls back to the
perldl shell transparently.
I don't see anything funny so the next step is to get
a short code
Uname doesn't give the amount of memory: 2.6.9-103.ELsmp #1 SMP Fri Dec 9
04:43:08 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
But /usr/bin/top shows it's 4 GB (which I think is buried down in the thread
below somewhere).
I set up some code to reproduce it, and discovered what the problem was.
