Issue 49433002: Work around two ASSERTs that we're hitting now that DEBUG is #defined again

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 49433002: Work around two ASSERTs that we're hitting now that DEBUG is #defined again (Closed)

Created:
7 years, 1 month ago by Jakob Kummerow

Modified:
7 years, 1 month ago

Reviewers:
danno

CC:
v8-dev

Base URL:
https://v8.googlecode.com/svn/branches/bleeding_edge

Visibility:
Public.

Work around two ASSERTs that we're hitting now that DEBUG is #defined again R=danno@chromium.org Committed: http://code.google.com/p/v8/source/detail?r=17418

Created: 7 years, 1 month ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+62 lines, -56 lines)			Patch
	M	src/compiler.cc	View		1 chunk	+59 lines, -55 lines	0 comments	Download
	M	src/objects-inl.h	View		1 chunk	+3 lines, -1 line	0 comments	Download

Total messages: 3 (0 generated)

Message was sent while issue was closed.

Committed patchset #1 manually as r17418.