CBMC shell script has different behaviour in different machines/OSs about cbmc

[tautschnig]

Does CBMC even provide a counterexample on MacOS for this benchmark? I wouldn't be surprised if --32 doesn't actually work on MacOS.

[lucasccordeiro]

I get no counterexample for this benchmark. I think the problem is this warning message:

./cbmc-wrapper: line 50: declare: -A: invalid option
declare: usage: declare [-afFirtx] [-p] [name[=value] ...]

I didn't have a chance to look further at this problem. I think my MacOS does not understand this:

declare -A OPTIONS
OPTIONS["label"]="--error-label"
OPTIONS["unreach_call"]=""
OPTIONS["termination"]=""
OPTIONS["overflow"]="--signed-overflow-check --no-assertions"
OPTIONS["memsafety"]="--pointer-check --memory-leak-check --bounds-check --no-assertions"

[tautschnig]

declare -A requires bash version 4. It would be possible to work around this by instead using multiple variables OPTIONS_label, OPTIONS_unreach_call, etc. and then construct the variable name at the point of use: var=OPTIONS_$PROP ; val=${!var}