|asan: directly report asan errors in system daemons|
|Project Member Reported by firstname.lastname@example.org, Nov 4 2013||Back to list|
In crosreview.com/38024, glotov@ directed chrome asan logs to a location in /var/log, and updated cbuildbot_commands to look for asan errors there. This provided the benefit of reporting asan errors even if they didn't cause an autotest to fail. We should generalize this for system daemons (e.g. shill, debugd). That's because system daemons are designed to restart and recover automatically. So it's possible for autotests to pass even if asan finds a bug in a system daemon.
Nov 5 2013,
Nov 8 2013,
@dkrahn: this is somewhat related to one of your requests.
Nov 11 2013,
yunlian was investigating this already. the last e-mail he sent stated: This is a work around at clang side. We can patch clang to set the default log_path to some other location.
Nov 11 2013,
Nov 14 2013,
Dec 14 2013,
Project: chromiumos/overlays/chromiumos-overlay Branch : master Author : Yunlian Jiang <email@example.com> Commit : 619c4b14821488bc4c5106303b92c2d18ba35c8c Code-Review 0 : Ahmad Sharif, Bhaskar Janakiraman, Caroline Tice, Han Shen, Luis Lozano, Simon Que, Yunlian Jiang, chrome-internal-fetch Code-Review +2: Mike Frysinger Commit-Queue 0 : Ahmad Sharif, Bhaskar Janakiraman, Caroline Tice, Han Shen, Luis Lozano, Mike Frysinger, Simon Que, chrome-internal-fetch Commit-Queue +1: Yunlian Jiang Verified 0 : Ahmad Sharif, Bhaskar Janakiraman, Caroline Tice, Han Shen, Luis Lozano, Mike Frysinger, Simon Que, chrome-internal-fetch Verified +1: Yunlian Jiang Change-Id : I7541202b1c2266e9d510709c718b0197f2f73d34 Reviewed-at : https://chromium-review.googlesource.com/177947 clang: change asan default output path. BUG= chromium:314678 TEST=the asan output now goes to /var/log/asan*.log sys-devel/clang/clang-3.4_pre188423-r1.ebuild sys-devel/clang/files/clang-3.4-asan-default-path.patch
Mar 3 2014,
I think this bug was fixed by the CL in #c6.
Mar 4 2014,
|► Sign in to add a comment|