Project

General

Profile

Bug #7983

VTG/ET shouldn't try to remove warning edges with tmp variables

Added by Anton Vasilyev about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Immediate
Category:
Tasks generation
Target version:
-
Start date:
02/17/2017
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

Memory problems could occur even on operations which involve temp variables.
Example http://ldvstore:8998/reports/component/94/293014/
Witness is attached.

VTG/ET throws exception:
File "/home/debian/klever/core/core/vtg/et/tmpvars.py", line 139, in __remove_tmp_vars removed_tmp_vars_num_tmp, next_edge = __remove_tmp_vars(error_trace, func_call_edge)
File "/home/debian/klever/core/core/vtg/et/tmpvars.py", line 197, in __remove_tmp_vars error_trace.remove_edge_and_target_node(tmp_var_use_edge)
File "/home/debian/klever/core/core/vtg/et/error_trace.py", line 212, in remove_edge_and_target_node raise ValueError('Cannot delete edge with warning: {!r}'.format(edge['source']))


Files

witness.0.graphml (124 KB) witness.0.graphml Anton Vasilyev, 02/17/2017 12:51 PM

History

#1

Updated by Evgeny Novikov about 3 years ago

  • Priority changed from High to Immediate

We don't need such dreadful errors at all.

#2

Updated by Evgeny Novikov about 3 years ago

  • Status changed from New to Closed

I fixed that in 979bae0 by moving more attributes from edges to be removed. Such the behavior wasn't possible for our usual rules, just for recently supported generic:memory and sync:race.

Also available in: Atom PDF