test/mjsunit/stack-traces.js - Issue 11554022: Fix stack trace recursion test.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: test/mjsunit/stack-traces.js

Issue 11554022: Fix stack trace recursion test. (Closed) Base URL: https://v8.googlecode.com/svn/branches/bleeding_edge

Patch Set: Created 8 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: test/mjsunit/stack-traces.js

diff --git a/test/mjsunit/stack-traces.js b/test/mjsunit/stack-traces.js

index 71d64191c106f979fdf715ba35c36a5c34417d62..d123df85fd37f4fd82373da2b6ad43bcdf1beec1 100644

--- a/test/mjsunit/stack-traces.js

+++ b/test/mjsunit/stack-traces.js

@@ -315,7 +315,7 @@ assertTrue(fired);

Error.prepareStackTrace = function() { throw new Error("abc"); }

var message;

try {

- throw new Error();

Erik Corry 2012/12/13 14:24:17 What's the logic here. Should both versions not w

+ new Error().stack;

} catch (e) {

message = e.message;

}

« no previous file with comments | « no previous file | no next file » | no next file with comments »