Files
mercury/tests/declarative_debugger/catch.exp
Zoltan Somogyi 33eb3028f5 Clean up the tests in half the test directories.
tests/accumulator/*.m:
tests/analysis_*/*.m:
tests/benchmarks*/*.m:
tests/debugger*/*.{m,exp,inp}:
tests/declarative_debugger*/*.{m,exp,inp}:
tests/dppd*/*.m:
tests/exceptions*/*.m:
tests/general*/*.m:
tests/grade_subdirs*/*.m:
tests/hard_coded*/*.m:
    Make these tests use four-space indentation, and ensure that
    each module is imported on its own line. (I intend to use the latter
    to figure out which subdirectories' tests can be executed in parallel.)

    These changes usually move code to different lines. For the debugger tests,
    specify the new line numbers in .inp files and expect them in .exp files.
2015-02-14 20:14:03 +11: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:26 (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:26 (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:37
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:26 (catch.m:17)
mdb> continue
exception(univ_cons("q: bad input"))
E5: C4 CALL pred catch.p/2-0 (cc_multi) catch.m:26 (catch.m:20)
mdb> finish
E6: C4 EXIT pred catch.p/2-0 (cc_multi) catch.m:26 (catch.m:20)
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:26 (catch.m:20)
mdb> continue
succeeded(2)