mirror of
https://github.com/Mercury-Language/mercury.git
synced 2026-04-16 01:43:35 +00:00
56509009dd
browser/declarative_oracle.m:
The code that checks whether the declarative debugger should trust
a module because it is a standard library module was apparently written
before any of module in the standard library had submodules, because
it checked the unqualified name of the module in question against
the *qualified* module names returned by the mercury_std_library_module
predicate.
For a long time after we had submodules such as thread.mvar.m in the
standard library, this caused no test failures, because our tests
did not execute code in those submodules. This changed with the breakup
of io.m. The move of the output_stream_2 predicate from io.m, which
this code recognized as trusted, to io.stream_ops.m, which it did not,
caused the declarative debugger to ask questions about the validity
of calls to it, which the caused the failure of the declarative_debugger/
all_trusted test case, due to its .inp file containing something other
than the corresponding answers.
Fix this for the case of module names of the forms a.b and a.b.c.
library/library.m:
Add a note to the mercury_std_library_module predicate to update
the code in declarative_oracle.m if we ever add a library module
whose fully qualified name has the form a.b.c.d.
tests/debugger/user_event_shallow.exp:
Update the expected output of this test for some ancient change.
tests/debugger/Mercury.options:
Specify the optimization level for the user_event_shallow test,
which eliminates one source of variability in the output.
Another source is intermodule optimization, which this diff does *not*
eliminate.
tests/debugger/all_solutions.exp:
tests/debugger/all_solutions.exp2:
tests/debugger/all_solutions.exp3:
tests/debugger/all_solutions.exp4:
tests/debugger/all_solutions.m:
The output of this test case in debug grades with intermodule optimization
did not match any of the .exp* files, though it differed from .exp2 only
in the text of an error message. (The difference was not a bug.)
Instead of adding this expected output as .exp5, use it to replace
the .exp3 file. This expected output file could not have been matched
in the last seven years, because it expects main/2 to be on line 16,
and that predicate's context has been line 20 since 2015.
Document the fact that .exp3 is the expected output for debug grade
bootchecks with intermodule optimization. This documentation changes
line numbers yet again, so update the line numbers in all the *other*
.exp* files as well.
tests/declarative_debugger/Mmakefile:
Fix indentation.
26 lines
924 B
Plaintext
26 lines
924 B
Plaintext
1: 1 1 CALL pred all_solutions.main/2-0 (det) all_solutions.m:26
|
|
mdb> echo on
|
|
Command echo enabled.
|
|
mdb> context none
|
|
Contexts will not be printed.
|
|
mdb> register --quiet
|
|
mdb> break hello
|
|
0: + stop interface pred all_solutions.hello/1-0 (multi)
|
|
mdb> continue
|
|
3: 3 3 CALL pred all_solutions.hello/1-0 (multi)
|
|
mdb> stack
|
|
0 pred all_solutions.hello/1-0 (multi)
|
|
1 pred solutions.builtin_aggregate/4-0 (cc_multi)
|
|
2 pred solutions.builtin_solutions/2-0 (cc_multi)
|
|
3 pred solutions.solutions/2-0 (det)
|
|
4 pred all_solutions.main/2-0 (det)
|
|
mdb> retry 1
|
|
Cannot perform retry because information about the input arguments is not available.
|
|
mdb> retry 2
|
|
Cannot perform retry because information about the input arguments is not available.
|
|
mdb> retry 3
|
|
2: 2 2 CALL pred solutions.solutions/2-0 (det)
|
|
mdb> continue -n -S
|
|
Hello again, world
|
|
Hello, world
|