DumpWithoutCrashing() is looking up wrong breakpad_win entry point.

DumpWithoutCrashing() is looking up wrong breakpad_win entry point.

DumpWithoutCrashing() was looking up DumpProcess instead of
DumpProcessWithoutCrash. The former generates a dialog to restart
chrome while the latter does not. Neither actually crashes the
browser process.

Prior to the CL, anything invoking DumpWithoutCrashing() would appear
to the user as if a crash had occurred, allowing the user to start
a new browser process/window, but leaving the original up and running
(unless the caller subsequently crashed the browser itself).

R= rtenneti@chromium.org, mseaborn@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=222393

[ramant (doing other things), 2013-09-09 18:31:34]

lgtm

thanks for the finding the bug and fixing it.

[Roger McFarlane (Chromium), 2013-09-09 20:14:19]

+jam for OWNERS

[jam, 2013-09-09 20:42:56]

lgtm

[commit-bot: I haz the power, 2013-09-10 13:09:42]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/rogerm@chromium.org/23484022/1

[commit-bot: I haz the power, 2013-09-10 16:11:47]

Commit queue had an internal error.
Something went really wrong, probably a crash, a hickup or
simply the monkeys went out for dinner.
Please email commit-bot@chromium.org with the CL url.

[commit-bot: I haz the power, 2013-09-10 21:40:22]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/rogerm@chromium.org/23484022/1

[commit-bot: I haz the power, 2013-09-10 23:25:23]

Change committed as 222393