Opened 16 years ago
Closed 16 years ago
#122 closed enhancement (fixed)
add option to not stop after finding violation
| Reported by: | Stephen Siegel | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Release 1.0 |
| Component: | verify | Version: | 1.0 |
| Keywords: | multiple error | Cc: |
Description
If the verifier can't prove an array index is in bounds, it could report the possible violation, save the trace, and then add the assumption that the index is in bounds and continue the search. Ditto for other classes of errors. This would allow the tool to find many errors at once.
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Component: | Administration → verify |
|---|---|
| Milestone: | → Release 1.0 |
comment:3 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Done. New commandline option -errorBound=N can be used to specify upper bound on number of errors found. Errors are categorized into equivalence classes and only one from each class is held.
Note:
See TracTickets
for help on using tickets.

We should also limit the amount of warnings to one warning per line of code/statement to prevent same warnings from being reported.