diff options
author | Alon Zakai <azakai@google.com> | 2020-04-13 07:58:10 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-04-13 07:58:10 -0700 |
commit | d7d251b75c46a814b764ff2ded0d9c5a275a7e46 (patch) | |
tree | 2be2f8c988b3057dc85e3e717276043de15e5397 /test | |
parent | 53c70d9ccd56d9d28eb65ccc5954024b6b0e921b (diff) | |
download | binaryen-d7d251b75c46a814b764ff2ded0d9c5a275a7e46.tar.gz binaryen-d7d251b75c46a814b764ff2ded0d9c5a275a7e46.tar.bz2 binaryen-d7d251b75c46a814b764ff2ded0d9c5a275a7e46.zip |
Use std::cout for interpreter trap logging (#2755)
We used std::cerr as a workaround for that this logging
interfered with spec testing. But it's easy enough to filter
out this stuff for the spec tests.
The benefit to using std::cout is that as you can see in
the test output here, this is relevant test output - it's not
a side channel for debugging. If the rest of the interpreter
output is in std::cout but only traps are in std::cerr then
they might end up out of order etc., so best to keep them
all together.
This will allow easier additions of tests for fuzz testcases
Diffstat (limited to 'test')
-rw-r--r-- | test/passes/fuzz-exec_O.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/test/passes/fuzz-exec_O.txt b/test/passes/fuzz-exec_O.txt index 095d301d1..841507f60 100644 --- a/test/passes/fuzz-exec_O.txt +++ b/test/passes/fuzz-exec_O.txt @@ -1,5 +1,7 @@ [fuzz-exec] calling func_0 +[trap final > memory: 18446744073709551615 > 65514] [fuzz-exec] calling func_1 +[trap final > memory: 18446744073709551615 > 65514] (module (type $none_=>_i32 (func (result i32))) (type $none_=>_i64 (func (result i64))) @@ -23,6 +25,8 @@ ) ) [fuzz-exec] calling func_0 +[trap final > memory: 18446744073709551615 > 65514] [fuzz-exec] calling func_1 +[trap final > memory: 18446744073709551615 > 65514] [fuzz-exec] comparing func_0 [fuzz-exec] comparing func_1 |