racluster 3.0.8.2 segfaults with -M dsrs option

[Carter Bullard via Argus-info]

Hey Markku P,
In looking at you data file, you’re only getting one side of all your traffic flow.  Could be a port mirroring problem ???
Carter


> On Jul 14, 2016, at 8:47 AM, Markku P via Argus-info <argus-info at lists.andrew.cmu.edu> wrote:
> 
> Hi,
> 
> My argus 3.0.8.1 has managed to produce few files that segfault even the latest racluster:
> 
> $ racluster -M dsrs=-agr -r crashing-20160703.dat -m proto  -w out.ra
> Segmentation fault
> 
> The issue seems to be on the "-M dsrs" option. The actual option value used does not seem to matter. Direct read with ra works normally. That same option works with most of my other files.
> 
> Trace:
> #0  0x0000000000457a81 in ArgusGenerateRecordStruct ()
> #1  0x0000000000432f4c in ArgusHandleRecord ()
> #2  0x0000000000459b7c in ArgusReadStreamSocket ()
> #3  0x0000000000459cb5 in ArgusReadFileStream ()
> #4  0x0000000000406482 in main ()
> 
> The system is an old CentOS 64bit linux, gcc 4.1.2.
> 
> I have uploaded that test file to qosient.com <http://qosient.com/> /incoming for your analysis.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20160714/230f006d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6285 bytes
Desc: not available
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20160714/230f006d/attachment.bin>