Temporary make the call stack trace around PasswordStore::WrapModificationTask more useful.

Temporary make the call stack trace around PasswordStore::WrapModificationTask more useful.

The patch is to be reverted a few days later when we have a crash report with the new stack trace.

BUG=396900
Committed: https://crrev.com/6aabbbf1afea5df0fab267302c7a1e19c30b649b
Cr-Commit-Position: refs/heads/master@{#311482}

[vasilii, 2015-01-14 14:30:11]

vasilii@chromium.org changed reviewers:
+ vabr@chromium.org

[vasilii, 2015-01-14 14:30:11]

Hi Vaclav,

please review the CL.

[vabr (Chromium), 2015-01-14 14:48:39]

This LGTM.

After a conversation with Vasilii, I understand that the change in the non-test
files is to be reverted once it helps investigate the stack traces, while the
change in the test files is a clean-up, which should stay.

Both of them LGTM, but I would prefer splitting them up in two CLs. This way
it's clear which part will get reverted, and the revert itself will be easier.

I'm happy to get TBR-ed on the split-off CL, as long as together the two CLs
produce the same diff a the current patch set 1.

Cheers,
Vaclav

[vasilii, 2015-01-14 14:50:01]

I reverted the changes to test_password_store.*.

[vasilii, 2015-01-14 14:50:09]

The CQ bit was checked by vasilii@chromium.org

[commit-bot: I haz the power, 2015-01-14 14:50:48]

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

[commit-bot: I haz the power, 2015-01-14 15:51:04]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-01-14 15:52:00]

Patchset 2 (id:??) landed as
https://crrev.com/6aabbbf1afea5df0fab267302c7a1e19c30b649b
Cr-Commit-Position: refs/heads/master@{#311482}