I have a 64-bit machine with 4GB memory. :-(

Any reason memory mapping won't achieve the same effect here?

On Tue, May 8, 2012 at 8:50 AM, Chris Marshall <marshallch@users.sourceforge.net> wrote:
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "pdl".

The branch, 64bit-index-support has been updated
      via  02a2351e2ba29aeb5c079a9f07bc86ca2f9838eb (commit)
     from  3779ba7f5880de92605342a19889c7e74fba7aef (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 02a2351e2ba29aeb5c079a9f07bc86ca2f9838eb
Author: Chris Marshall <devel.chm.01@gmail.com>
Date:   Tue May 8 09:45:35 2012 -0400

   Change strtol to strtoll in slices.pd

   I hope this will fix some of the failures from
   slicing operations reported by Ingo.  Still have
   other issues but still no-one able to directly
   debug on a 64bit system.

   If you have a 64bit system, more than 4GB of memory
   and are able to perform PDL+XS/PP debugging, your help
   would be greatly appreciated.  It is *very* difficult
   to make progress without being able to gdb or printf
   to locate the source of fails.  I think we're getting
   close but until the low level stuff is working, we're
   not able to merge these hardwired 64bit support mods
   into the master.


Summary of changes:
 Basic/Slices/slices.pd |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)


Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
pdl-commit mailing list

 "Debugging is twice as hard as writing the code in the first place.
  Therefore, if you write the code as cleverly as possible, you are,
  by definition, not smart enough to debug it." -- Brian Kernighan