rabins 3.0.3.22 -t <year>/... unusable on 32-bit Ubuntu10.04

[carter at qosient.com]

Hey Wolfgang,
Sorry for the delay.  If you run with -D 2 or 3, you should see how the 32bit version is parsing the time range specification.  We allocate an array of bins for the entire time range, so if it is confused, like thinking the starting time is 0, then it will not do well allocating 4G of pointers.

What does it think?

Carter 
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Wolfgang Barth <wob at swobspace.de>
Sender: argus-info-bounces+carter=qosient.com at lists.andrew.cmu.edu
Date: Sun, 6 Feb 2011 12:02:09 
To: <argus-info at lists.andrew.cmu.edu>
Reply-To: wob at swobspace.de
Subject: [ARGUS] rabins 3.0.3.22 -t <year>/... unusable on 32-bit Ubuntu
	10.04

Hi Carter,

I try to get rabins working on a 32bit machine (Ubuntu 10.04 LTS), but I'm
running in the problem with -t:

* ra -r logfile -t 2011/02/06 ... works
* rabins -M time 1m -t 2011/02/06 ... no output
* rabins -M time 1m .... works
* rabins -M time 1m -t 10-12 ...
  rabins[16126]: 11:48:31.012680 ArgusCalloc: malloc error Cannot allocate memory
  ... last data is 11:40, so 12:00 ist behind the end of data.

I tried sensor data from argus-3.0.3.19 and argus-3.0.3.22, same effect. If
I process the same logfile on Ubuntu 10.04 64bit, rabins works fine.

And something very special:

* rabins -M time 1m -r logfile -t '****/02/06'

works on 32-bit, but not the following:

* rabins -M time 1m -r logfile -t '2011/**/**'
  rabins[27993]: 11:58:26.207773 ArgusCalloc: malloc error Cannot allocate memory

So, the problem occurs on my 32 bit plattform only if I specify the year
with rabins. ra and racluster are working for me.

How can I help you to do more debugging?

Wolfgang
-- 
<wob (at) swobspace de> * http://www.swobspace.de