See information about integrating Breakpad and creating minidump in Breakpad integration to RDK-V component page

Overview

Crash upload component helps in uploading the crashes (coredump or minidump files) that happened in the set-top boxes to the crash portal server(which can be configured). Crash portal collects crash dumps and logs which happened in the connected STBs, process these and provide a meaningful backtrace.

Crash Portal server processes 2 types of crash dump files

Minidumps

• Minidump files are a lightweight crash dump format developed by Microsoft.
• Google Breakpad project supplies tools to work with Minidump files.
• The primary tool used by Crash Portal is minidump_stackwalk which generates a stack trace from a minidump file.
• See http://www.chromium.org/developers/decoding-crash-dumps

Coredumps

• Coredump files are standard Linux coredumps.
• Crash Portal extracts information from the coredump files but does not generate a stack trace.
  • But a tool such as gdb will do this.

CrashUpload

Minidump or core files are tarred and uploaded by crashUpload component:

https://code.rdkcentral.com/r/plugins/gitiles/rdk/components/generic/crashupload

dump-backup.service invokes /lib/rdk/core_shell.sh which is responsible for calling uploadDumps.sh script to upload the crash dump to crash portal server.

    echo "|$RDK_PATH/core_shell.sh %e %s %t" >/proc/sys/kernel/core_pattern

uploadDumps.sh script collects the following and compresses it to create a .tgz format

• minidump file (*.dmp)
• version.txt
• ocapri_log.txt
• messages.txt
• core_log.txt

CrashPortal URL should be configured in the /lib/rdk/uploadDumps.sh script

eg:

     PORTAL_URL="35.155.171.121:80"

     REQUEST_TYPE=17

Crash Portal System Architecture