Overview

Crash dumping system facilitates service providers or developers to collect crashes happened in the set-top boxes and do the debugging in offline. Crash dumping system is a debug supporting system, which consists of Crash dumping server(s) with user interfaces.  Crash dumping server collect crash logs which happened in the connected STBs, process these logs and store for future reference.

Crash log is a log file automatically created on Set top boxes when a crash occurs. This information is useful for offline debugging. 

Minidump

• A list of the executable and shared libraries that were loaded in the process at the time the dump was created. This list includes both file names and identifiers for the particular versions of those files that were loaded.
• A list of threads present in the process. For each thread, the minidump includes the state of the processor registers, and the contents of the threads' stack memory.
• Other information about the system on which the dump was collected: processor and operating system versions, the reason for the dump, and so on. 

Google Breakpad

Breakpad is a library that records crashes in compact "minidump" files. It  produce C and C++ stack traces from minidumps. Breakpad can also write minidumps on request for programs that have not crashed. 

...

How to Integrate Google Breakpad library?

...

• A minidump will be generated in the same file

Coredump

Core dump files generated after an uncaught signal in a process (as a SIGSEGV or SIGQUIT), are generated in the base directory where the program was executed, and the core dumps starts with the name  as “core” or “core.PID”.

...

gdb <executable_path> <coredump_file_path>

(gdb) bt full

API Documentation

To know more about SoC/Application level APIs details use in RDK, refer the link  Crashupload API Documentation