Current plan of action is:
- stop collecting stacktrace right before reporting and use information we had in ConsoleMessage;
- instrument places lacking stacktrace and rebaseline layout tests;
- move stacktrace collection from ad-hoc places to ConsoleMessage::create.
The final API would be:
- if you pass location (url + line + optional column) to ConsoleMessage::create, it doesn't capture stack;
- if you only pass the message, it does capture the stack.
Comment 1 by dgozman@chromium.org
, May 14 2016