goto_trace: unbounded integers are now shown like other numbers

[kroening]

• Each commit message has a non-empty body, explaining why the change was made.
• n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
• Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
• n/a My commit message includes data points confirming performance improvements (if claimed).
• My PR is restricted to a single feature or bugfix.
• White-space or formatting changes outside the feature-related changed lines are in commits of their own.

[allredj]

🚫
This PR failed Diffblue compatibility checks (cbmc commit: f73969c).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/90165384
Status will be re-evaluated on next push.
Please contact @peterschrammel, @thk123, or @allredj for support.

Common spurious failures:

• the cbmc commit has disappeared in the mean time (e.g. in a force-push)
• the author is not in the list of contributors (e.g. first-time contributors).

The incompatibility may have been introduced by an earlier PR. In that case merging this
PR should be avoided unless it fixes the current incompatibility.

[tautschnig]

Do the SMT-solver backed tests exercise this bit of code? If so, could an explicit test be added?

[kroening]

We can add a test either if
a) we activate the SMT-backend tests and have a solver that supports unbounded integers; or
b) we add (at least basic) support for unbounded integers to the internal solver.

[tautschnig]

We already have regression/cbmc/integer-assignments1, maybe that should include some patterns to inspect the trace output?

[kroening]

Indeed, done

[tautschnig]

The parentheses will need escaping. (CI currently passes as we don't have SMT in there yet.)

[kroening]

done

[allredj]

🚫
This PR failed Diffblue compatibility checks (cbmc commit: a4462eb).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/90246246
Status will be re-evaluated on next push.
Please contact @peterschrammel, @thk123, or @allredj for support.

Common spurious failures:

• the cbmc commit has disappeared in the mean time (e.g. in a force-push)
• the author is not in the list of contributors (e.g. first-time contributors).

The incompatibility may have been introduced by an earlier PR. In that case merging this
PR should be avoided unless it fixes the current incompatibility.

[allredj]

✔️
Passed Diffblue compatibility checks (cbmc commit: 4e87b90).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/90264632