Issue 196132: Print a stacktrace when we can't find a string resource (on Windows).

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 196132: Print a stacktrace when we can't find a string resource (on Windows). (Closed)

Created:
11 years, 3 months ago by Paweł Hajdan Jr.

Modified:
9 years, 7 months ago

Reviewers:
bradnelson, bradn

CC:
chromium-reviews_googlegroups.com

Visibility:
Public.

Print a stacktrace when we can't find a string resource (on Windows). This should help debug the linked bug, or at least rule out some possibilities. TEST=none BUG=21925 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=26297

Created: 11 years, 3 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+3 lines, -0 lines)			Patch
	M	app/resource_bundle_win.cc	View		3 chunks	+3 lines, -0 lines	0 comments	Download

Total messages: 2 (0 generated)

LGTM