Linux Driver Verification

Feature #2421

Updated by Evgeny Novikov over 12 years ago

We have missed this earlier indeed. I found a hard-coded 'blast' verifier engine in KB routines that helped to process BLAST error traces and use such the circumstance: 
 <pre> 
 return 1 if (call_stacks_ne($et, $kb_et)); 
 </pre> 
 while the correct one should be like this: 
 <pre> 
 return 1 if (call_stacks_ne($et, 'engine1', $kb_et, 'engine2')); 
 </pre> 
 ('engine1' may equal to 'engine2'). 
 This completely fails when an engine used isn't blast. 
 By means of a header specified for a error trace processed it'll be clear what engine should be used.

Back