Feature #1633
openKB: library function to check if assertion failed in a function given
0%
Description
It looks like the most useful library function for KB scripts is a function that checks if the assertion failed is within the given function (with arbitrary nesting level).
Updated by Evgeny Novikov about 13 years ago
- Category set to Statistics server
- Status changed from New to Open
- Assignee set to Evgeny Novikov
If so, it should be done. But before it it seems to me that we should integrate KB scripts with error trace parser of error-trace-visualizer that creates internal, independent on verifier representation of an error trace. Also we should think a bit about this library organization.
Updated by Alexey Khoroshilov about 13 years ago
- Priority changed from Normal to High
Updated by Evgeny Novikov over 11 years ago
Now default criterion used for error traces comparison is "call stacks":
return 1 if (call_stacks_ne($et, $kb_et));It obtains two arrays of function names leading to ldv_error on the basis of two error traces and compares them.
In these terms this feature request asks for ability to specify an user's partial call stack (instead of call stack extracting from a stored error trace) to be used in comparison with a call stack of a new error trace. I guess following notation:
my $call_stack = ["..", "func1", "func2", "..", "func3", ".."];
return 1 if (call_stacks_ne($et, $call_stack));
What do you think?