crash_reporter should include failure reasons in its log messages |
|||
Issue descriptionFrom crbug.com/760337: 017-09-07T14:28:54.770878+08:00 ERR crash_reporter[1812]: Could not get active user sessions, using default. 2017-09-07T14:28:54.794204+08:00 ERR crash_reporter[1812]: Failed to gzip /home/chronos/crash/chrome.20170907.142854.1721.chrome.txt 2017-09-07T14:28:54.807593+08:00 ERR crash_reporter[1812]: Unable to write /home/chronos/crash/chrome.20170907.142854.1721.meta We lose the crash data in this case :( We should write the reason for the failed writes to help with debugging these.
,
Sep 8 2017
> just to be clear, you mean "we should include the failure reason in the log message" :) ? Yes, that would have been a better title :) Peeking at the crash_reporter source, it looks like /home/chronos/crash is used as a fallback when there's no active user, and I thought that /home/chronos should exist regardless. It looks like you wrote that fallback logic, though, so I trust your analysis ;)
,
Aug 1
|
|||
►
Sign in to add a comment |
|||
Comment 1 by vapier@chromium.org
, Sep 8 2017