Handle stack frames differently inside and on the boundary of wasm.

src/log.cc

Index: src/log.cc
diff --git a/src/log.cc b/src/log.cc
index 294596c396277d59453054830dc754245b116731..0bebf8dcf3301551d90c386a9b4a8c1b60c5188b 100644
--- a/src/log.cc
+++ b/src/log.cc
@@ -1576,7 +1576,15 @@ void Logger::LogCodeObject(Object* object) {
       tag = Logger::KEYED_STORE_IC_TAG;
       break;
     case AbstractCode::WASM_FUNCTION:
-      description = "A wasm function";
+      description = "A Wasm function";
+      tag = Logger::STUB_TAG;
+      break;
+    case AbstractCode::JS_TO_WASM_FUNCTION:
+      description = "A JavaScript to Wasm thunk";

[titzer, 2016/03/03 23:25:05]

thunk sounds so violent! We generally use the term adapter for such frames.

[bradn, 2016/03/03 23:28:49]

Done.

+      tag = Logger::STUB_TAG;
+      break;
+    case AbstractCode::WASM_TO_JS_FUNCTION:
+      description = "A Wasm to JavaScript thunk";
       tag = Logger::STUB_TAG;
       break;
   }