search

google / sawbuck

Automatically exported from code.google.com/p/sawbuck
106 stars 40 forks source link

error 0x80070570 when trying to read Google Chrome debug_log #133

Open AddaxSoft opened 4 years ago

AddaxSoft commented 4 years ago

I followed the instructions here https://support.google.com/chrome/a/answer/6271282?hl=en Here is a sample of my chrome_debug.log from notepad.exe

[4832:5556:1102/235240.817:VERBOSE1:machine_level_user_cloud_policy_controller.cc(111)] DM token = none
[4832:5556:1102/235240.817:VERBOSE1:machine_level_user_cloud_policy_controller.cc(112)] Enrollment token = 
[4832:5556:1102/235240.817:VERBOSE1:machine_level_user_cloud_policy_controller.cc(113)] Client ID = 49926***************
[4832:5556:1102/235240.879:VERBOSE1:webrtc_event_log_manager.cc(99)] WebRTC remote-bound event logging enabled.
[4832:5556:1102/235240.879:VERBOSE1:pref_proxy_config_tracker_impl.cc(184)] 0000028D89395680: set chrome proxy config service to 0000028D8BC86CB0

Sawbuck cannot open chrome_debug.log; instead it displays this error: image

Windows 10 Chrome Version 78.0.3904.87 (Official Build) (64-bit)

AySz88 commented 4 years ago

Unless there's an event trace file for Sawbuck being dropped somewhere unknown to me, it appears those instructions are incorrect - this Chromium documentation does not suggest that Sawbuck parses chrome_debug.log at all, but rather should be configured to capture and log the relevant data while Chrome runs.