cc: DCHECK if SDOS::SwapBuffersComplete is called prematurely

cc: DCHECK if SDOS::SwapBuffersComplete is called prematurely

This is for debugging purposes only and will be reverted
soon.

BUG=495650
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/5ea9e525a197fb1a55c38db8d1c739771e520fbd
Cr-Commit-Position: refs/heads/master@{#333667}

[brianderson, 2015-06-10 00:12:30]

brianderson@chromium.org changed reviewers:
+ jbauman@chromium.org

[brianderson, 2015-06-10 00:12:30]

John recommended trying something like this to gather more info while looking at
the problem locally.

ptal

[jbauman, 2015-06-10 00:17:46]

lgtm

https://codereview.chromium.org/1175703004/diff/1/cc/surfaces/surface_display...
File cc/surfaces/surface_display_output_surface.cc (right):

https://codereview.chromium.org/1175703004/diff/1/cc/surfaces/surface_display...
cc/surfaces/surface_display_output_surface.cc:25: inside_swap_buffers_(false) {
0

[sunnyps, 2015-06-10 00:20:37]

On 2015/06/10 00:12:30, brianderson wrote:
> John recommended trying something like this to gather more info while looking
at
> the problem locally.
> 
> ptal

BTW you can also print the stack trace on debug builds using base::StackTrace.

[brianderson, 2015-06-10 00:21:53]

On 2015/06/10 00:20:37, sunnyps wrote:
> On 2015/06/10 00:12:30, brianderson wrote:
> > John recommended trying something like this to gather more info while
looking
> at
> > the problem locally.
> > 
> > ptal
> 
> BTW you can also print the stack trace on debug builds using base::StackTrace.

I will give that a try too. Any idea if it gives better results than the stack
traces we are already getting in the logs?

[brianderson, 2015-06-10 00:36:25]

The CQ bit was checked by brianderson@chromium.org

[brianderson, 2015-06-10 00:36:25]

The patchset sent to the CQ was uploaded after l-g-t-m from jbauman@chromium.org
Link to the patchset: https://codereview.chromium.org/1175703004/#ps40001
(title: "stack traces")

[commit-bot: I haz the power, 2015-06-10 00:44:23]

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

[commit-bot: I haz the power, 2015-06-10 03:09:05]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-06-10 03:10:06]

Patchset 3 (id:??) landed as
https://crrev.com/5ea9e525a197fb1a55c38db8d1c739771e520fbd
Cr-Commit-Position: refs/heads/master@{#333667}