ra seg fault on 1.8 beta code
cbullard at nortelnetworks.com
Mon Jun 14 11:45:16 EDT 1999
Found the problem. Bad index number for array of strings.
The complete fix is a little more than this, but if you make
this patch, then things will work much better until I get
the next set of fixes ready.
Here's the diff.
< processStr = process_state_strings;
> processStr = process_state_strings;
Hope this helps and thanks!!!!
From: Peter Van Epp [mailto:vanepp at sfu.ca]
Sent: Friday, June 11, 1999 5:25 PM
To: argus at sei.cmu.edu
Subject: ra seg fault on 1.8 beta code
Ra is seg faulting (probably because of bad fragmentation from where
it is) on an argus capture file. However gdb isn't thinking it wants to let
me look at any of the variables after the seg fault and the capture file is
a little large (138 megs uncompressed) to send to you. Can you suggest a way
to either extract a piece of the capture file or display something from the
ra seg fault under gdb that would be useful to you?
#0 0x280b3960 in strcat ()
#1 0xefbfd860 in ?? ()
#2 0x80498bc in process_tcp (ptr=0xefbfda40) at ./ra.c:227
#3 0x804c519 in version_process (ptr=0xefbfda40) at ./argus_parse.c:1310
#4 0x804ad6d in handle_datum (ptr=0xefbfdaa4, bpfcode=0xefbfdc78)
#5 0x804c3ff in read_file (fd=6, bpfcode=0xefbfdc78) at ./argus_parse.c:1275
#6 0x804a119 in main (argc=4, argv=0xefbfdcbc) at ./argus_parse.c:351
#7 0x8049379 in _start ()
(gdb) x/x 0xefbfda40
0xefbfda40 <__atexit+2948519340>: 0x09002430
This is the beta 1.8 code that Carter sent me a month or so back (which
is working fine by the way) on a FreeBSD 3.1 box.
Peter Van Epp / Operations and Technical Support
Simon Fraser University, Burnaby, B.C. Canada
More information about the argus