Issue 151145: Experimental: capture 10 frame stack trace by default.

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

Issue 151145: Experimental: capture 10 frame stack trace by default. (Closed)

Created:
11 years, 5 months ago by Christian Plesner Hansen

Modified:
9 years, 7 months ago

Reviewers:
Søren Thygesen Gjesse

CC:
v8-dev

Visibility:
Public.

Description

Enable capture of the top of the stack on error instantiation. Performance impact on v8 benchmarks seems limited. Will be backed out if chrome performance regresses.

Patch Set 1 #

Created: 11 years, 5 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+44 lines, -30 lines)			Patch
M	src/bootstrapper.cc	View	1 chunk	+7 lines, -9 lines	0 comments	Download
M	src/flag-definitions.h	View	1 chunk	+1 line, -1 line	0 comments	Download
M	src/messages.js	View	1 chunk	+6 lines, -2 lines	0 comments	Download
M	src/runtime.h	View	1 chunk	+1 line, -1 line	0 comments	Download
M	src/runtime.cc	View	1 chunk	+29 lines, -15 lines	0 comments	Download
M	test/mjsunit/stack-traces.js	View	1 chunk	+0 lines, -2 lines	0 comments	Download

Messages

Total messages: 2 (0 generated)

Expand Messages | Collapse Messages

LGTM

Expand Messages | Collapse Messages