[Mojo] ApplicationRunnerChromium should dump stacks in debug

[Mojo] ApplicationRunnerChromium should dump stacks in debug

This behavior matches what we do in renderer_main.cc.

R=jamesr@chromium.org

Committed: https://crrev.com/72a65e46a0ae1000662856838179f3ee46a2b6c1
Cr-Commit-Position: refs/heads/master@{#299961}

[eseidel, 2014-10-16 17:00:31]

eseidel@chromium.org changed reviewers:
+ eseidel@chromium.org

[eseidel, 2014-10-16 17:00:32]

Blink/Chrome is going to want to do similar as well, along with ripping out
WTF's signal handlers and backtrace printing.

[jamesr, 2014-10-16 17:30:58]

lgtm

[abarth-chromium, 2014-10-16 19:40:09]

The CQ bit was checked by abarth@chromium.org

[commit-bot: I haz the power, 2014-10-16 19:41:20]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/658113003/1

[commit-bot: I haz the power, 2014-10-16 19:48:05]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-10-16 19:53:11]

Patchset 1 (id:??) landed as
https://crrev.com/72a65e46a0ae1000662856838179f3ee46a2b6c1
Cr-Commit-Position: refs/heads/master@{#299961}

[jochen (gone - plz use gerrit), 2014-10-17 06:52:34]

On 2014/10/16 at 17:00:32, eseidel wrote:
> Blink/Chrome is going to want to do similar as well, along with ripping out
WTF's signal handlers and backtrace printing.

the content module invokes this method already. The WTF signal handlers are
unused, we could just remove them.

Removing the backtrace printing would require adding a dependency on base/
(which might make sense anyways)