Files
mercury/tests/declarative_debugger/catch.exp
Zoltan Somogyi ecb5e4a9e6 Update the style of many test cases.
tests/declarative_debugger/*.m:
tests/exceptions/*.m:
tests/general/*.m:
tests/grade_subdirs/*.m:
tests/purity/*.m:
tests/submodules/*.m:
tests/typeclasses/*.m:
    Update programming style.

tests/declarative_debugger/*.inp:
    Update line numbers in breakpoint commands.
tests/declarative_debugger/*.exp:
    Update expected line numbers.

tests/exceptions/Mercury.options:
tests/general/Mercury.options:
    Disable some warnings that are irrelevant to the test.
2021-07-25 23:26:17 +10:00

50 lines
1.4 KiB
Plaintext

E1: C1 CALL pred catch.main/2-0 (cc_multi) catch.m:16
mdb> echo on
Command echo enabled.
mdb> register --quiet
mdb> break p
0: + stop interface pred catch.p/2-0 (cc_multi)
mdb> continue
E2: C2 CALL pred catch.p/2-0 (cc_multi) catch.m:24 (catch.m:17)
mdb> finish
mdb: warning: reached unknown label
This may result in some exception events
being omitted from the trace.
E3: C2 EXIT pred catch.p/2-0 (cc_multi) catch.m:24 (catch.m:17)
mdb> dd -d 3 -n 7
mdb: warning: reached unknown label
This may result in some exception events
being omitted from the trace.
p(1, exception(univ_cons("q: bad input")))
Valid? no
Call q(1, _)
Throws "q: bad input"
Expected? no
Found unhandled or incorrect exception:
q(1, _)
"q: bad input"
Is this a bug? yes
E4: C3 EXCP pred catch.q/2-0 (det) e;c3; catch.m:33
mdb> continue
mdb: warning: reached unknown label
This may result in some exception events
being omitted from the trace.
E3: C2 EXIT pred catch.p/2-0 (cc_multi) catch.m:24 (catch.m:17)
mdb> continue
exception(univ_cons("q: bad input"))
E5: C4 CALL pred catch.p/2-0 (cc_multi) catch.m:24 (catch.m:19)
mdb> finish
E6: C4 EXIT pred catch.p/2-0 (cc_multi) catch.m:24 (catch.m:19)
mdb> dd -d 3 -n 7
p(2, succeeded(2))
Valid? no
q(2, 2)
Valid? yes
Found incorrect contour:
q(2, 2)
p(2, succeeded(2))
Is this a bug? yes
E6: C4 EXIT pred catch.p/2-0 (cc_multi) catch.m:24 (catch.m:19)
mdb> continue
succeeded(2)