radium core dump, 3.0.5.32

[Mark E. Mallett]

Howdy,

(I'm new here)

I am getting a core dump in radium from argus-clients-3.0.5.32 on a
64bit Arch Linux system. The coredump happens in in 3-0.5.32 but not in
3-0.5.31. The two versions were built the same way.

The core dump happens when I use any ra* client (or at least any that
I've tried) to connect to the radium server and also specify an input
filter for a srcid.

It's easy to reproduce here with a simple radium.conf file like this:

RADIUM_MONITOR_ID=`hostname`
RADIUM_CISCONETFLOW_PORT=9996
RADIUM_ACCESS_PORT=561
RADIUM_BIND_IP=myhostname
RADIUM_ARGUS_SERVER=127.0.0.1:561

(substitute something real for "myhostname")

The ARGUS_SERVER being referenced is running with a srcid of 127.0.0.1
I want to select records only from that source (btw, the
RADIUM_ARGUS_SERVER line doesn't have to be present; i.e., the radium
server doesn't have to be listening to that source, but it probably
makes the usage example clearer).

radium is being started simply:
   radium -w [somefilename]

If I run a ra* client and ask for records from the 127.0.0.1 source, e.g.:
  ra -N 5 -S myhostname:561 - srcid 127.0.0.1
no problem. Run it again:
  ra -N 5 -S myhostname:561 - srcid 127.0.0.1
then radium coredumps, and the ra* client reports "remote Filter error"

if I do the same with radium from 3-0.5.31 the ra* client runs fine
every time.  I also rebuilt the 3-0.5.31 package to make sure the
development environment hadn't changed.

I noticed it first with ratop, but tried it with various other ra* clients.

Sometimes the radium server gives a stack trace, sometimes it doesn't.
The stack trace starts out with a double free error from glibc.

I'd be happy to give more info if needed, or take feedback if I'm
doing something wrong :-)

Yours,
-mm-