Current all udev collected reports have the same signature and
exec_name. This patch makes that different udev rules generate
reports with different signatures and exec_name so that it is
easier to search a specific kind of udev report on crash server.
BUG=chromium-os:35169
TEST=Tested locally, with a fake udev rule
ACTION=="change", SUBSYSTEM=="i2c", DRIVER=="cyapa", ENV{ERROR}=="1", RUN+="/sbin/crash_reporter --udev=SUBSYSTEM=i2c-cyapa:ACTION=change"
and fake crash_reporter_logs.conf entry
crash_reporter-udev-collection-change--i2c-cyapa:grep -C 20 cyapa /var/log/messages
Generate a report log with meta data:
"
sig=crash_reporter-udev-collection-change--i2c-cyapa
exec_name=udev-i2c-cyapa
ver=3120.0.2012_10_31_1248
payload=/var/spool/crash/change__i2c_cyapa.20121102.125731.0.log.gz
payload_size=6557
done=1
"
Change-Id: I9f7905b69e786a2a13cb8a8df46eeba243157009
Reviewed-on: https://gerrit.chromium.org/gerrit/37262
Reviewed-by: Simon Que <sque@chromium.org>
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Commit-Ready: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>
Udev collector compresses crash log and appends .gz as file extension
which is not recognized by crash sender. This patch fixes crash sender
by extracting real file extension if the original log file ends with
.gz.
BUG=chromium-os:35968
TEST=Manually test, crash sender can send udev collector generated
log file: report id 7fa1184e8e62946f.
Change-Id: Ic0abd9f264ef601399cc5edd27faa6f64cd9f204
Reviewed-on: https://gerrit.chromium.org/gerrit/37136
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Simon Que <sque@chromium.org>
Commit-Ready: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>
For crash reports sent when a machine is in developer mode, annotate them
with a "boot_mode" key set to "dev". This is so other people know the
system may have been mucked with.
BUG=chromium-os:33947
TEST=Ran logging_CrashSender autotest
Change-Id: I30d58885e41f2c32e32b7b0f691ed2e5d14f2e3c
Reviewed-on: https://gerrit.chromium.org/gerrit/33246
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
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>
I somehow missed "AudioOutputDevice" as the name of a Chrome thread. It
showed up in crash reports.
BUG=chrome-os-partner:12045
TEST=Ran unittests
Change-Id: Ia29404aebfe806a81fceb6b45145434af6749822
Reviewed-on: https://gerrit.chromium.org/gerrit/33224
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
For crash reports sent from developer images, annotate them with an
"image_type" key set to "dev". This is so other people know they can be
ignored. The key will be set to "force-official" if the $FORCE_OFFICIAL
environment variable is set for non-developer images.
BUG=chromium-os:33947
TEST=Ran logging_CrashSender autotest
Change-Id: I9d87bdc7dac1a9fd4898fb3c7fd1c965c81d4ce3
Reviewed-on: https://gerrit.chromium.org/gerrit/32480
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
At some point Chrome started naming its threads such that crashes report a
different executable name. We've been getting a *lot* of crash-reporter
errors with names like "supplied_Compositor" in particular, so consider
those to be Chrome crashes that should be ignored.
Unfortunately, the thread names can be arbitrary. With this CL we check the
entire range of possible names. Maybe someday someone can use the core file
to determine that a process was originally named "chrome".
BUG=chrome-os-partner:12045
TEST=Ran unittests
Change-Id: Ia82d619bd1ee4367129640dc6c7be5ce258a68bb
Reviewed-on: https://gerrit.chromium.org/gerrit/31084
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
The current build logic assumes the build dir is directly under the
source dir. This fails if the build and source trees are completely
different paths. So use a full path to the source dir rather than a
relative one so that it works in all states.
BUG=chromium-os:33327
TEST=`cros_run_unit_tests --board x86-alex -p crash-reporter` still works
Change-Id: I0e6b4c257cbef5879cb67e8692e3082bbb5fb2d5
Reviewed-on: https://gerrit.chromium.org/gerrit/29577
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Previously added a udev collector to CrashCollector. Now it's time to
put it in its own class.
BUG=chromium-os:30268
TEST=See "TEST=" under https://gerrit.chromium.org/gerrit/21498
Change-Id: I6a62826cb84ef7ccd42a512b00e127af6de3280d
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/25112
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
SendEnumToUMA() and SendCrashToUMA() are being called from three
functions in crash_reporter.cc. This patch puts the three calls
plus a repeated TODO into one helper function that's called by the
three existing functions.
BUG=chromium-os:11163,chromium-os:30268
TEST=emerge crash-reporter
Change-Id: I703d93e3a072faa0264a220a69df2203af100c57
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26291
Reviewed-by: Ben Chan <benchan@chromium.org>
BUG=chrome-os-partner:6492
TEST=Run:
"crash_reporter --udev=ACTION=change:KERNEL=card0:SUBSYSTEM=drm"
Check that a card0-drm log.gz file has been created under /var/spool/crash
Check that the corresponding .meta file points to the log.gz file.
Change-Id: Id1ecc82b9fac118f8bf1e5edc40c3a2f61abd4c4
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/21495
Reviewed-by: Ben Chan <benchan@chromium.org>
The KernelCollectorTest.CollectBadDirectory unittest was first re-enabled by
sergiu@ in https://gerrit.chromium.org/gerrit/5433, but it broke the
buildbots and had to be re-disabled. So I'm trying again, but this time I
have the power of trybots! I also added code to output the log if it fails
again.
BUG=chromium-os:18622
TEST=Ran unittests. Ran trybots on: alex-paladin, amd64-generic-paladin,
arm-tegra2-paladin, lumpy-paladin, stumpy-paladin.
Change-Id: Ib7fa1c1a32e9c198db9bdae8f933c9dd9fc3381a
Reviewed-on: https://gerrit.chromium.org/gerrit/20667
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
Rather than disable the "format not a string literal, argument types not
checked" warning for the entire kernel_collector.cc file, only disable it
for the code in question.
BUG=chromium-os:27127
TEST=Ran unittests
Change-Id: Id85e7945779cd5d1b6a3b68cfdedae53b3f22c74
Reviewed-on: https://gerrit.chromium.org/gerrit/20484
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
This will allow running of unittests on ARM, as well as cleaning up the make
output some.
BUG=chromium-os:27127
TEST=Ran unittests, logging_CrashSender, and logging_UserCrash
Change-Id: Ide09a42132be0843146dde6687e4424352b6b866
Reviewed-on: https://gerrit.chromium.org/gerrit/20174
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
The CantDisable test was failing because it couldn't properly fake the
enabling of the crash collector -- which meant that the disable didn't
actually fail. The reason was that the "test" directory was being removed
during SetUp(). I also added/improved some error-checking that helped me
track down various unittest failures.
BUG=chromium-os:29395
TEST=Ran unittests
Change-Id: I8cf50dbd0d5187b0028c8cf16ae10a4f68bb160f
Reviewed-on: https://gerrit.chromium.org/gerrit/20129
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
This allows crash_reporter to handle nonfatal errors from the kernel
passed thru udev events. There is a udev .rules file for invoking crash
reporter. Currently it supports DRM error info logging.
BUG=chrome-os-partner:6492
TEST=Run:
"crash_reporter --udev=ACTION=change:KERNEL=card0:SUBSYSTEM=drm"
Check that a card0-drm log file has been created under /var/spool/crash
Change-Id: I05a1d508e5446988575b0c1924878b8e36ae46bb
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/10618
If the "error_type" field was set by crash_reporter (see benchan@'s
https://gerrit.chromium.org/gerrit/17166), then send it with the crash
report. This currently only affects crashes with the
"crash_reporter-user-collection" error signature.
BUG=chromium-os:7871
TEST=Manually ran crash_sender
Change-Id: I34c5e055efb407d57a3f83b07e8d4fc0a6b8fac1
Reviewed-on: https://gerrit.chromium.org/gerrit/19641
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
FindCrashingFunction() fails to find the crashing kernel function because
the x86 64bit kernel code (arch/x86/kernel/dumpstack.c:die()) issues "RIP"
instead of "EIP". So it falls back to using the panic string in the crash
signature.
This causes the logging_KernelCrash.py test to fail because it looks for the
crashing function in the signature string.
BUG=chromium-os:22353
TEST=logging_KernelCrash
Change-Id: Ic4790648facf5f0be2b82001f8e18b606eca16c7
Reviewed-on: https://gerrit.chromium.org/gerrit/19492
Reviewed-by: Ben Chan <benchan@chromium.org>
Tested-by: Bryan Freed <bfreed@chromium.org>
Commit-Ready: Bryan Freed <bfreed@chromium.org>
BUG=chromium-os:27821
TEST=emerge crash-reporter and verified the updated crash_reporter_logs.conf is installed.
Change-Id: Id2b7de30b36eaa57e6251261d8bca6810d5e8b82
Reviewed-on: https://gerrit.chromium.org/gerrit/18181
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
This includes a couple of fixes:
- use the right compiler flag names
- execute pkg-config twice total, and not once per compile
- build against SLOT-ed libbase
BUG=chromium-os:16623
TEST=`emerge-x86-alex crash-reporter` still works
TEST=`cros_run_unit_tests --board x86-alex -p crash-reporter` passes
Change-Id: I76fdf552de1c0e10367475f3ad22b6b0b33bfa66
Reviewed-on: https://gerrit.chromium.org/gerrit/17709
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Kees Cook <keescook@chromium.org>
This CL makes the following changes to improve error diagnostics in
UserCollector:
1. Add an error type to describe why the crash reporter fails to
collects a user crash, which is reported to the crash server along
with the "crash_reporter-user-collection" error signature.
2. Perform some preliminary validations of the core file before
converting it to a minidump file using core2md.
3. Identify the case when a 32-bit core file is produced on a 64-bit
platform as core2md currently cannot handle 32-bit core files on
a 64-bit platform.
BUG=chromium-os:7871
TEST=Tested the following:
1. emerge-{x86,amd64,arm}-generic crash-reporter
2. FEATURES="test" emerge-{x86,amd64,arm}-generic crash-reporter
3. Run the following autotest tests on x86-mario and stumpy64:
- logging_CrashSender
- logging_UserCrash
Change-Id: Ib50b4cc81a91f7cd75f9440005200d4027ce1f6f
Reviewed-on: https://gerrit.chromium.org/gerrit/17166
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
This CL fixes the KernelCollectorTest.LoadPreservedDump test due to
KernelCollector::records_ not being initialized. It also updates
KernelCollectorTest.CollectPreservedFileMissing and
KernelCollectorTest.CollectNoCrash.
BUG=chromium-os:27126
TEST=Tested the following:
1. emerge-{x86,amd64,arm}-generic crash-reporter
2. FEATURES="test" emerge-{x86,amd64,arm}-generic crash-reporter
Change-Id: If5a773fa77a2e66e539d204410140d1b4e66d062
Reviewed-on: https://gerrit.chromium.org/gerrit/17125
Reviewed-by: Kees Cook <keescook@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Make sure that once collected, a crash report is removed from the pstore
filesystem so that the memory is cleared to avoid endless crash
duplicates.
BUG=chromium-os:26496
TEST=lumpy build & boot, triggered crashes ("echo bug > /proc/breakme") are
saved to /var/spool/crash and removed from pstore.
STATUS=Fixed
Change-Id: Ic224f5880cdc34d1f75470ac71f27fcad146ff4b
Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/16501
Reviewed-by: Olof Johansson <olofj@chromium.org>
Reviewed-by: Bryan Freed <bfreed@chromium.org>
The kernel-crash-detected and unclean-shutdown-detected flag files
needed to move out of /tmp to protect against symlink attacks by
a non-root user. /var/run is owned by root, so non-privileged
users can't write there.
BUG=chromium-os:17085
TEST=unit
TEST=logging_CrashSender,logging_UserCrash
STATUS=Fixed
Change-Id: Ibf9b314f1a03ee984eea2acf6007c120aa300dd1
Reviewed-on: https://gerrit.chromium.org/gerrit/16751
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Kees Cook <keescook@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
The ebuild no longer installs this, so punt it.
BUG=chromium-os:25750
TEST=`emerge crash-reporter` still works
Change-Id: I94416b44ee87cc282a80128f5a3b2f190a191184
Reviewed-on: https://gerrit.chromium.org/gerrit/15402
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This reverts commit 490634ffaefa3b3b93c623e376674ab5cd3763c8
Change-Id: I593c57ccd527d1294439ec730c3b805862fefd70
Reviewed-on: https://gerrit.chromium.org/gerrit/14122
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
This CL fixes commit c7c7914f49fbdef0d1f06c13854daabe176621ed such that
UserCollector continues to read the core file from stdin even if the proc
files are unusable.
BUG=chromium-os:24820
TEST=Tested the following:
1. Build crash-reporter and run unit tests.
2. Run the following autotest tests on a Cr48:
- logging_CrashSender
- logging_UserCrash
Change-Id: I04d09b15a80344b47f0512196c40e94384c5c323
Reviewed-on: https://gerrit.chromium.org/gerrit/13872
Reviewed-by: Ken Mixter <kmixter@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
This CL makes the following changes to UserCollector:
1. Check if the maps file is empty after copying proc files to the
temporary container directory, which prevents the core-to-minidump
conversion failure due to unusable maps file.
2. Obtain and log the state of the crashed process, which helps
determine if the crashed process is in the zombie state.
3. Refactor the status file processing code.
BUG=chromium-os:24820
TEST=Tested the following:
1. Build crash-reporter and run unit tests.
2. Run the following autotest tests on a Cr48:
- logging_CrashSender
- logging_UserCrash
3. Check that the process state of a crashed process is logged in
/var/log/messages.
Change-Id: Iebaf9c36c18185c703c18e7028ee4673dd9ebc93
Reviewed-on: https://gerrit.chromium.org/gerrit/13826
Reviewed-by: Ken Mixter <kmixter@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
With this change the crash reporter tries to determine if the last stack
dump in the log file is from the hung thread watchdog, and in that case
creates a crash signature that's based on the previous stack dump.
When the previous stack is used because the watchdog function was detected,
prepend "(HANG)" to the function name or kernel message in the signature.
Also use an earlier stack signature if all functions in the last one are
uncertain. This happens in many cases (about 1/2). It's likely a
bug in the kernel but until we fix it this workaround will be helpful.
I tested this manually with the --generate_kernel_signature flag and
with the provided unit test. I also added two unit tests for the two
new cases. Finally, I tried to run the KernelCrashServer autotests,
but it doesn't run correctly in developer mode, even before my change.
BUG=chromium-os:24632
TEST=manually tested, unit tested, and autotested. No further tests required.
Change-Id: Ib65177b06c207675cb7f6e33f1df8fa79dde6090
Reviewed-on: https://gerrit.chromium.org/gerrit/13541
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
Tested-by: Luigi Semenzato <semenzato@chromium.org>
Commit-Ready: Luigi Semenzato <semenzato@chromium.org>
This CL modifies UserCollector to copy procfs files of a crashed process
into /tmp/crash_reporter/<pid> instead of /tmp/crash_reporter.<pid>.
The new directory layout makes it easier for autotest to archive
leftover files under /tmp/crash_reporter due to core2md failures.
BUG=chromium-os:24646
TEST=Tested the following:
1. Build crash-reporter and run unit tests.
2. Run the following autotest tests on a Cr48:
- logging_CrashSender
- logging_UserCrash
Change-Id: I435374eabc1574216881318ddacdfa9d1648c875
Reviewed-on: https://gerrit.chromium.org/gerrit/13697
Commit-Ready: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Use the new ramoops pstore interface instead of reading /dev/mem or
needing to know anything about the ramoops memory configurations.
BUG=chromium-os:12059
TEST=x86-alex build and boot, logging_KernelCrashServer passes,
local "make tests" passes.
Change-Id: Ie713d4f93df7f666537c7181b1b438d7b85d4861
Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/11245
Reviewed-by: Will Drewry <wad@chromium.org>
This reverts commit 4a029228b93edcd9cf79c2578acd27eb56be5bce
Although this passes in my local checkout, it broke the buildbots. Will investigate more.
Change-Id: Ib6e33bb916b43b1a42f8f8e4c0c69eb360c3181c
Reviewed-on: http://gerrit.chromium.org/gerrit/8332
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
Activated the BadDirectory test which was breaking the build.
BUG=chromium-os:18622
TEST=Ran the unit tests locally and it succeded.
Change-Id: I439d9fb40ec37261ef839c82817d6bc67e683c7d
Signed-off-by: Sergiu Iordache <sergiu@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/5433
Reviewed-by: Ken Mixter <kmixter@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
Some of the types being used happened to work on 32bit systems because
size_t is pretty much an unsigned int. But with a 64bit system, we see:
kernel_collector.cc: In member function
'virtual bool KernelCollector::LoadParameters()':
kernel_collector.cc:141: error: cannot convert 'size_t*' to 'unsigned int*'
for argument '2' to 'bool LoadValue(FilePath, unsigned int*)'
This is easy to fix by using the correct type in LoadValue().
Next up, we get a failure due to the assumption that int64 can be
displayed using the lld format string. But on 64bit systems, this
doesn't work:
crash_collector.cc: In member function
'void CrashCollector::WriteCrashMetaData(const FilePath&, const std::string&, const std::string&)':
crash_collector.cc:355: error:
format '%lld' expects type 'long long int', but argument 6 has type 'int64'
This takes a little bit more magic to make work. Since printf itself
does not provide a printf string to handle "64bit" types, use the macros
that POSIX provides in inttypes.h. The printf string is a little uglier,
but now should work for all targets.
BUG=chromium-os:20636
TEST=`emerge-amd64-generic crash-reporter` now works
TEST=`emerge-x86-generic crash-reporter` still works
TEST=build+booting x86-alex still works
Change-Id: I8401f2ad932223085dfbe54541590e9b65297783
Reviewed-on: http://gerrit.chromium.org/gerrit/8051
Reviewed-by: Ken Mixter <kmixter@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Added HWID query via crossystem if not available via ACPI. This populates
the hwclass field for crash reports.
BUG=None
TEST=Manually confirmed ARM platform crash reports contains correct hwclass
and manually confirmed ZGB report contains previously reported hwclas
Change-Id: I1216ed13c0b04d829313103d3bb736f5227a772b
Reviewed-on: http://gerrit.chromium.org/gerrit/7982
Reviewed-by: Doug Anderson <dianders@chromium.org>
Reviewed-by: Micah Catlin <micahc@chromium.org>
Commit-Ready: Katie Roberts-Hoffman <katierh@chromium.org>
Tested-by: Katie Roberts-Hoffman <katierh@chromium.org>
The old crash reporter used preserved to get the memory dump. Updated it
to use the upstream ramoops module. Also updated the unit tests.
Depends on other patches related to this bug report:
The backport series starting with:
http://gerrit.chromium.org/gerrit/#change,5342 until 5347 (included)
The series starting with: http://gerrit.chromium.org/gerrit/#change,5426
until 5429 (included)
http://gerrit.chromium.org/gerrit/#change,5159
BUG=chromium-os:12059
TEST=Ran module unit tests, ran logging_KernelCrashServer and
platform_KernelErrorPaths, checked manually that the
crash file existed.
Change-Id: I37bdb30513acfab79997e478af5de35ca33557fd
Signed-off-by: Sergiu Iordache <sergiu@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/5432
Reviewed-by: Ken Mixter <kmixter@chromium.org>
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
If the file "/mnt/stateful_partition/etc/collect_chrome_crashes" exists on
the target, dump crashes to /var/spool/crash/ instead of
/home/chronos/user/crash/. This is so they are easily available even after
logout.
BUG=chromium-os:18637
TEST=Ran unit and remote tests.
Change-Id: I340bbb0c1772123192c8bb87872bcda53fae5524
Reviewed-on: http://gerrit.chromium.org/gerrit/5419
Reviewed-by: Ken Mixter <kmixter@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
Treecloser filed as crosbug.com/18622; temporarily disabling this test to reopen
the tree.
BUG=chromium-os:18622
TEST=Not anymore
Change-Id: I4b7467f6044e02ab1308f449d5aa530a15535933
Signed-off-by: Elly Jones <ellyjones@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/5214
Reviewed-by: Chris Masone <cmasone@chromium.org>
If the file "/mnt/stateful_partition/etc/collect_chrome_crashes" exists on
the target, allow chrome crashes to be reported by crash reporter. The
intention is that the autotest system will create this file. This is a
relatively temporary fix to help track down chrome problems, until the
crashes can be handled by crash reporter in the field as well.
BUG=chromium-os:17987, chromium-os:17898
TEST=Ran unit tests.
Change-Id: I68a584a0b861669117d8e97f5687b4c8fc876011
Reviewed-on: http://gerrit.chromium.org/gerrit/4861
Reviewed-by: Ken Mixter <kmixter@chromium.org>
Tested-by: Ken Mixter <kmixter@chromium.org>
BUG=chromium-os:6828
TEST=Manually ran crash_sender to make sure it would run curl with appropriate --proxy option. Manually ran curl using proxies from "http://proxyconfig.corp.google.com/wpad.dat". Ran a modified crash_sender manually to make sure it passed the appropriate "--proxy" arguments correctly.
Review URL: http://codereview.chromium.org/6802003
Change-Id: Ie1414fca1a7dbc265d8aad0eea32a736a5d30d54
Create a list_proxies command to be used by crash_sender to determine the correct proxy for a URL. This uses D-Bus to get them from either the browser or the session manager.
BUG=chromium-os:6828
TEST=Ran list_proxies command manually to test response for various URLs: "http://...", "https://...", empty/NULL, and invalid (eg. just "blah.com"). Also did this for the various proxy settings in the browser: direct, manual proxy configuration, and automatic proxy configuration. Ran list_proxies command using invalid D-Bus method name for proxy_resolver.StartMonitoring() to make sure timeout works. Ran a modified crash_sender manually to make sure it passed the appropriate "--proxy" arguments correctly.
Review URL: http://codereview.chromium.org/6730021
Change-Id: I738a4544f90218ffc7c2d36547de49b462ca749e
This reverts commit 59d8695734dac2ce70b17d2a58049083e65e997d.
My original commit did not actually break anything, so this just puts it back.
BUG=chromium-os:13576
TEST=unit tests, logging_{UserCrash,CrashSender} autotests
Review URL: http://codereview.chromium.org/6765017
Change-Id: I5b9ebb2b210b86fb4efaf49c71dcd2562805c973
