Adjustments to modbus test cases.

- Added a test for binpac exception handling -- the generated code
  should use "binpac::Exception" and not "Exception" for exception
  handling logic to avoid accidental overshadowing by
  the analyzer-specific type "binpac::ModbusTCP::Exception", which
  could lead to interesting asserts being triggered in binpac.

- Update baseline for the event coverage test -- seems that more
  events get generated with working exception handling in the generated
  binpac parser code.

- Coverage baseline was giving wrong number of events covered.
This commit is contained in:
Jon Siwek 2012-11-12 11:51:42 -06:00
parent aac922d7af
commit defed7b6f3
9 changed files with 301 additions and 5 deletions

View file

@ -0,0 +1,11 @@
#separator \x09
#set_separator ,
#empty_field (empty)
#unset_field -
#path modbus
#open 2012-11-12-17-40-34
#fields ts uid id.orig_h id.orig_p id.resp_h id.resp_p func exception
#types time string addr port addr port string string
1153491909.414125 UWkUyAuUGXf 192.168.66.235 2582 166.161.16.230 502 unknown-156 -
1153491913.013726 UWkUyAuUGXf 192.168.66.235 2582 166.161.16.230 502 unknown-162 -
#close 2012-11-12-17-40-34

View file

@ -0,0 +1,11 @@
#separator \x09
#set_separator ,
#empty_field (empty)
#unset_field -
#path weird
#open 2012-11-12-17-40-34
#fields ts uid id.orig_h id.orig_p id.resp_h id.resp_p name addl notice peer
#types time string addr port addr port string string bool string
1153491909.414066 - - - - - truncated_IP - F bro
1153491912.529443 UWkUyAuUGXf 192.168.66.235 2582 166.161.16.230 502 binpac exception: out_of_bound: WriteSingleRegisterRequest: 4 > 0 - F bro
#close 2012-11-12-17-40-34