mirror of
https://github.com/Mercury-Language/mercury.git
synced 2026-04-17 10:23:46 +00:00
33eb3028f5
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.
32 lines
1.0 KiB
Plaintext
32 lines
1.0 KiB
Plaintext
E1: C1 CALL pred poly_io_retry.main/2-0 (det) poly_io_retry.m:18
|
|
mdb> mdb> Contexts will not be printed.
|
|
mdb> echo on
|
|
Command echo enabled.
|
|
mdb> table_io allow
|
|
mdb> table_io start
|
|
I/O tabling started.
|
|
mdb> break polycall
|
|
Ambiguous procedure specification. The matches are:
|
|
0: pred poly_io_retry.polycall/3-0 (det)
|
|
1: pred poly_io_retry.polycall/3-1 (det)
|
|
|
|
Which do you want to put a breakpoint on (0-1 or *)? *
|
|
0: + stop interface pred poly_io_retry.polycall/3-0 (det)
|
|
1: + stop interface pred poly_io_retry.polycall/3-1 (det)
|
|
mdb> c
|
|
E2: C2 CALL pred poly_io_retry.polycall/3-0 (det)
|
|
mdb> f
|
|
1
|
|
E3: C2 EXIT pred poly_io_retry.polycall/3-0 (det)
|
|
mdb> retry -a
|
|
E2: C2 CALL pred poly_io_retry.polycall/3-0 (det)
|
|
mdb> f
|
|
E3: C2 EXIT pred poly_io_retry.polycall/3-0 (det)
|
|
mdb> c
|
|
E4: C3 CALL pred poly_io_retry.polycall/3-1 (det)
|
|
mdb> f
|
|
E5: C3 EXIT pred poly_io_retry.polycall/3-1 (det)
|
|
mdb> retry
|
|
Cannot perform retry because the values of some input arguments are missing.
|
|
mdb> quit -y
|