diff options
| author | 2022-08-09 13:14:10 +0100 | |
|---|---|---|
| committer | 2022-08-09 14:27:46 +0000 | |
| commit | 9c38a4e33e19b5846ba1126b5547449ab0a66f69 (patch) | |
| tree | 678dbd3485087d78d12409cc3f7b5c50c4e72a4b | |
| parent | 5bd4a63facdc3abb209a2550775bdbae19b7fccf (diff) | |
Copy crash_dump from device to chroot.
The crash_dump binary and tombstoned running on the device share a
protocal format. So copy crash_dump from the device to the chroot to
ensure we get stack traces when ART crashes in the chroot.
Test: HelloWorld with a crash, see stack trace in logcat
Change-Id: I50bd7d2471c8322e895203c08184bd5262c3748f
| -rwxr-xr-x | tools/buildbot-sync.sh | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/tools/buildbot-sync.sh b/tools/buildbot-sync.sh index 28dab0ce04..f8af1a20ed 100755 --- a/tools/buildbot-sync.sh +++ b/tools/buildbot-sync.sh @@ -111,6 +111,13 @@ activate_apex com.android.tzdata activate_apex com.android.conscrypt activate_apex com.android.os.statsd +# Replace the crash dump binary with the one on the device. This is because +# the tombstoned server running is the one on the device. +msginfo "Copying crash_dump from device to chroot" +for b in {32,64}; do + adb shell "cp /apex/com.android.runtime/bin/crash_dump$b $ART_TEST_CHROOT/apex/com.android.runtime/bin" +done + # Generate primary boot images on device for testing. for b in {32,64}; do basename="generate-boot-image$b" |