From ab1a4bd15ed0d9e8c8ecbffd62e11e2c78ff1f28 Mon Sep 17 00:00:00 2001 From: Tristan Gingold Date: Mon, 25 May 2020 19:48:09 +0200 Subject: grt: implement --backtrace-severity. For #1338 --- doc/using/Simulation.rst | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) (limited to 'doc/using') diff --git a/doc/using/Simulation.rst b/doc/using/Simulation.rst index c73a379d8..e90d061b3 100644 --- a/doc/using/Simulation.rst +++ b/doc/using/Simulation.rst @@ -64,8 +64,17 @@ Here is the list of the most useful options. For further info, see :ref:`DEV:Deb stop simulation, but the assertion violation at the ``note`` severity level would only display a message. - Option :option:`--assert-level=none <--assert-level>` prevents any assertion violation from stopping - simulation. + Option :option:`--assert-level=none <--assert-level>` prevents any + assertion violation from stopping simulation. + +.. option:: --backtrace-severity= + + Select the assertion level at which an assertion violation display a + backtrace (if available). + + This is useful when the assertion is generated by a function (like + assertions in ``ieee.numeric_std``) whose location is not very + useful. .. option:: --ieee-asserts= -- cgit v1.2.3