From 36d22d82aa202bb199967e9512281e9a53db42c9 Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Sun, 7 Apr 2024 21:33:14 +0200
Subject: Adding upstream version 115.7.0esr.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 .../tests/ion/recover-lambdas-bug1113940.js        | 37 ++++++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 js/src/jit-test/tests/ion/recover-lambdas-bug1113940.js

(limited to 'js/src/jit-test/tests/ion/recover-lambdas-bug1113940.js')

diff --git a/js/src/jit-test/tests/ion/recover-lambdas-bug1113940.js b/js/src/jit-test/tests/ion/recover-lambdas-bug1113940.js
new file mode 100644
index 0000000000..078e51ad2c
--- /dev/null
+++ b/js/src/jit-test/tests/ion/recover-lambdas-bug1113940.js
@@ -0,0 +1,37 @@
+
+gczeal(14);
+
+// The object metadata callback can iterate over the stack. Thus during the
+// allocation of the lambda we might inspect the stack which is still incomplete
+// because the lambda is not yet reconstructed.
+//
+// enableShellAllocationMetadataBuilder ignores its argument, because we don't
+// permit metadata callbacks to run JS any more, so this test may be
+// unnecessary. We'll preserve its structure just in case.
+enableShellAllocationMetadataBuilder(function() {});
+function f() {
+    (function() {
+        '' ^ Object
+    })();
+}
+x = 0;
+for (var j = 0; j < 99; ++j) {
+    x += f();
+}
+
+try {
+  x = true;
+  // Same comment as above.
+  enableShellAllocationMetadataBuilder(function([x, y, z], ... Debugger) {});
+  for (var i = 0; i < 10; ++i) {
+    var f = function() {
+      function g() {
+	x++;
+      }
+      g();
+    }
+    f();
+  }
+} catch (e) {
+  assertEq(e instanceof TypeError, true);
+}
-- 
cgit v1.2.3