Download Bound-T Reference Manual - Bound

Warning options (-warn)
The following Table 21 lists the item values that can be used with the -warn option. Multiple
-warn options can be given, with cumulative effect. For example, the command
boundt -warn access -warn symbol ...
turns on warnings for unresolved dynamic memory accesses and for multiply defined symbols.
Several items can be listed in the same option, separated by commas (but without whitespace),
in this way:
boundt -warn access,symbol ...
The rightmost column in the table shows the default warning options. By using items with the
no_ prefix you can cancel these defaults. Note also that there are many kinds of warnings that
cannot be controlled with this option and are always enabled.
Table 21: Options for warnings
56
-warn item
Warnings affected
access
Instructions that use unresolved dynamic data access (pointers).
call
Calls with unbounded execution time or stack usage.
computed_return
Calls with dynamically computed return addresses.
eternal
Eternal loops that have no exit and thus cannot terminate.
file_match
Source-file names from mark definitions that now match (or do
not match) source-file names from the target program's
debugging information, but would not match (or would match)
under a different setting of the -file_match option.
flow
Jumps and calls with dynamically computed target address.
large
Instructions that contain or involve literal values too large to be
analysed as defined by the option -calc_max.
reach
Instructions, loops or calls that become unreachable (infeasible),
in part or in whole, through analysis or assertions. See the
discussion of flow-graph pruning in section 2.6.
return
Calls to subprograms that never return.
role
An assertion on the role of an instruction was not used, because
the instruction was not analysed, or because its role is fixed.
sign
Instructions that contain literal values with an uncertain sign,
where the value can interpreted as an unsigned or signed (two's
complement) value.
sub_miss
Subprograms for which assertions are present (in the -assert files)
but which are not found in the program under analysis. The
assertions are therefore not used and are irrelevant to the
analysis.
symbol
Symbols that have multiple definitions in the target-program
symbol-table, that is, symbols that are ambiguous even when fully
qualified by scope (see section 3.3).
The Bound-T Command Line
Default?
Bound-T Reference Manual
Yes
Yes
Yes
Yes
Yes