ACPR/android_system_core
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

crash-reporter: Don't send dmesg output with internal crash_reporter reports

Browse source 
Seeing as kernel crashes no longer include dmesg output, we probably
shouldn't either.  This is for crash reports with signature
"crash_reporter-user-collection".

BUG=chromium-os:34389
TEST=Ran logging_UserCrash autotest
CQ-DEPEND=I813a711c3557227cc17a58be8f960bfe569722bc

Change-Id: I52debf6d8ad32132d3b64c7f313f306b26287dd1
Reviewed-on: https://gerrit.chromium.org/gerrit/33167
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
This commit is contained in:
Michael Krebs 2012-09-12 20:31:20 -07:00 • committed by Gerrit
parent a1cc38388b
commit bc2d7dde16
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
crash_reporter/crash_reporter_logs.conf
View file

@ -25,7 +25,7 @@ cros_installer:cat $(ls -1tr /var/log/update_engine | tail -5 | sed s.^./var/log
# as it is stored in memory. The output format specified for 'ps' is the
# same as with the "u" ("user-oriented") option, except it doesn't show
# the commands' arguments (i.e. "comm" instead of "command").
crash_reporter-user-collection:echo "===ps output==="; ps axw -o user,pid,%cpu,%mem,vsz,rss,tname,stat,start_time,bsdtime,comm | tail -c 25000; echo "===dmesg output==="; dmesg | tail -c 25000; echo "===meminfo==="; cat /proc/meminfo
crash_reporter-user-collection:echo "===ps output==="; ps axw -o user,pid,%cpu,%mem,vsz,rss,tname,stat,start_time,bsdtime,comm | tail -c 25000; echo "===meminfo==="; cat /proc/meminfo
# This rule is similar to the crash_reporter-user-collection rule, except it is
# run for kernel errors reported through udev events.