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

1 files changed, 1 insertions, 1 deletions

diff --git a/src/shell-interface.h b/src/shell-interface.h
index 94ecd61c3..a5293ac76 100644
--- a/src/shell-interface.h
+++ b/src/shell-interface.h
@@ -218,7 +218,7 @@ struct ShellExternalInterface : ModuleInstance::ExternalInterface {
   }
 
   void trap(const char* why) override {
-    std::cerr << "[trap " << why << "]\n";
+    std::cout << "[trap " << why << "]\n";
     throw TrapException();
   }
 };