Argus 2.00{B,E} woes

[Carter Bullard]

Hey William,
   Well this is a new line of code, so it could definitely
generate new problems.  This should be an easy fix, and
I'll have it in "F" tomorrow.

Carter

-----Original Message-----
From: owner-argus at lists.andrew.cmu.edu
[mailto:owner-argus at lists.andrew.cmu.edu]On Behalf Of William Setzer
Sent: Monday, November 27, 2000 4:47 PM
To: argus at lists.andrew.cmu.edu
Subject: Argus 2.00{B,E} woes


Two quick updates.  I was still getting:

  ArgusError: ArgusUpdateFlow() fragment parent confusion.

with "B" over the last weekend.  I haven't seen one on "E" yet, but
I've only been running it a few hours.

However, in both "B" and "E", I've started getting the occasional
segmentation fault. (I don't think I saw one before "B".)  In the four
times I've checked it, it looks to have all been in the same place:

  Core was generated by `/local/new/argus_dlpi -i ge0 -P 0 -w
/local/disk/0/argus'.
  Program terminated with signal 11, Segmentation Fault.
  Cannot access memory at address 0xef7ed25c.
  #0  0x1aa00 in ArgusUpdateFlow (flowstr=0x1bad8b0, state=Cannot access
memory at address 0xeffff4f7.
  ) at ./ArgusModeler.c:451
  451           if (((ArgusThisIpHdr->ip_off & 0x1fff) == 0) &&
(ArgusThisIpHdr->ip_off & IP_MF)) {
  (gdb) p ArgusThisIpHdr
  $1 = (struct ip *) 0x0

This is under Solaris 2.6 reading a pretty loaded gigabit link.


William
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20001127/d206a445/attachment.html>