Time Travel Debugging with WinDbg

[Benjamin Beaudry]

Hi folks,

Does anyone ever used the Time Travel Debug feature of WinDbg for Chromium? When I try it, Chromium simply stops responding. My early investigation points to a sandbox issue, so I tried running the chromium executable with the "--no-sandbox" flag, without success.

Any help would be appreciated!

Best,

Ben

[Bruce Dawson]

You may want to ask @aluhrs13 on twitter - they work on WinDbg and with Edge now being Chromium based they have an extra incentive to get this to work.

I used TTD on IE9 many years ago and it worked very well and was quite helpful.

[Christian Biesinger]

This is with Windbg Preview? I've used it successfully with content_shell, but I've only used it with --single-process myself.

Christian

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/94529e49-886f-4733-905a-8dd23948df92%40chromium.org.

[Sim on]

afair, TDD isn't compatible with multiple-processes programs

[Bruce Dawson]

I thought TDD worked with multiple processes but it's been a long time, and the public version may be different from the internal.

Apparently deadlocks when tracing Chromium are known (https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/time-travel-debugging-overview):

"Another example of an environment that conflicts with TTD, would be the electron application framework. In this case the trace may record, but a deadlock or crash of the process being recorded is also possible."

I'll follow-up offline.

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---

You received this message because you are subscribed to a topic in the Google Groups "Chromium-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/chromium-dev/zlJcxZRJ8gw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/d121019a-52d0-47ba-82bd-4fc4a9b7edd0%40chromium.org.

[Bruce Dawson]

I checked with some windbg contacts and they said that Time Travel Debugging should work with multiple processes and with Chromium. They're not sure how the claims of deadlocks when tracing Electron came from and are looking in to that.

The sandbox is an issue if you connect TTD to a renderer process after the token has been dropped but shouldn't be a problem if you are connected from the start.

The Chromium sampling profiler could potentially cause issues - maybe try disabling that? If that is a continual problem then we can explore disabling the sampling profiler when TTD is detected, similarly to how we are going to disable it when App Verifier is detected.

If you still have issues then reporting a bug would be the next best step. If you use the Windows 10 feedback hub or other mechanisms and then send the bug link to twitter.com/aluhrs13 or then it should get looked at.

[18楼梦想改造家]

Debug the release chromium version is ok, debug version is very hard....