Bug testcase for curr_pc sync issue

tests/ecmascript/test-bug-currpc-sync-gh294.js

@@ -0,0 +1,78 @@
+/*
+ *  Some curr_pc sync bugs when developing GH-294.
+ */
+
+/*===
+calling inner
+inner called
+-1 0
+-2 23
+-3 30
+-4 35
+inner returned
+===*/
+
+/* When a function call is made, act->curr_pc must be synced so that
+ * inner functions can see correct numbers in e.g. stacktraces, debugger
+ * GetCallStack, Duktape.act(), etc.
+ */
+
+function funcCallTest() {
+    function inner() {
+        print('inner called');
+        for (i = -1; (t = Duktape.act(i)) != null; i--) {
+            print(i, t.lineNumber);
+        }
+        return 123;
+    }
+
+    print('calling inner');
+    inner();
+    print('inner returned');
+}
+
+try {
+    funcCallTest();
+} catch (e) {
+    print(e.stack || e);
+}
+
+/*===
+testing
+getter called
+-1 0
+-2 62
+-3 70
+-4 75
+123
+done
+===*/
+
+/* The executor may do an automatic function call when it accesses a setter.
+ * Curr_pc must be synced for these too.  This is automatic if syncing is done
+ * by call handling.
+ */
+
+function sideEffectTest() {
+    var obj = {};
+    Object.defineProperty(obj, 'prop', {
+        get: function () {
+            var i, t;
+            print('getter called');
+            for (i = -1; (t = Duktape.act(i)) != null; i--) {
+                print(i, t.lineNumber);
+            }
+            return 123;
+        }
+    });
+
+    print('testing');
+    print(obj.prop);
+    print('done');
+}
+
+try {
+    sideEffectTest();
+} catch (e) {
+    print(e.stack || e);
+}