📖
Qwertycoin Documentation
  • Introduction to Qwertycoin
  • Getting Started
    • Terminology
    • Simple Steps
  • Wallet
    • Types of Wallet
    • Paper Wallet
    • CLI Wallet
    • GUI Wallet
    • Zero Wallet
    • Mobile Wallet
    • Web Wallet
    • RPC Wallet
    • Wallet Backup
    • Wallet Recovery
    • Wallet Update
    • Sign and Verify Messages
  • Mining
    • Mining Options
    • Cloud Mining
    • Creating a Mining Pool
    • Mining With SBC
    • Mobile Mining
    • Using a Mining Pool
    • XMR-Stak
    • XMR-Stak Linux
    • XMRIG
  • Node (Daemon)
    • Configuration
    • Fix Sync Issues
    • Load Checkpoints
    • Start Masternode
  • Trading
    • Exchanges
    • How to Trade on BISQ
    • How to Trade on CREX24
  • Developer
    • Compiling Daemon from Source
      • MacOS QT Install
      • Install Cmake 3.14
    • Forking Qwertycoin
    • Google Breakpad Integration
    • Hosting Block Explorer
    • Hosting Web Wallet
    • Hosting Faucet
    • Local Testnet
    • Resources
  • API
    • Daemon HTTP RPC Commands
    • Daemon JSON RPC API
    • Wallet RPC API
Powered by GitBook
On this page
  • Overview
  • Getting Readable Stack Trace from User Submitted Files

Was this helpful?

  1. Developer

Google Breakpad Integration

PreviousForking QwertycoinNextHosting Block Explorer

Last updated 5 years ago

Was this helpful?

Overview

After crash occurs and intercepted by breakpad it creates minidump file (*.dmp) with useful crash related information. Extracting human readable information from minidump file format requires running of minidump_stackwalk tool with specially pre-generated symbol files on application binaries.

Getting Readable Stack Trace from User Submitted Files

  1. Original should be checked out on dev machine and built locally;

  2. Use dump_syms tool to generate symbols file from application binary file:

google-breakpad/src/tools/linux/dump_syms/dump_syms ./ApplicationBinary > ./ApplicationBinary.sym
head -n1 ./ApplicationBinary.sym

Above command output may look something like this:

MODULE Windows x86_64 6EDC6ACDB282125843FD59DA9C81BD830 ApplicationBinary
  1. To structure symbols file correctly you can do following next:

mkdir -p ./symbols/ApplicationBinary/6EDC6ACDB282125843FD59DA9C81BD830
mv ./ApplicationBinary.sym ./symbols/ApplicationBinary/6EDC6ACDB282125843FD59DA9C81BD830
  1. Generate readable stack trace pointing to the place with crash by running minidump_stackwalk tool on minidump file with passing the path to previously generated symbol files:

google-breakpad/src/processor/minidump_stackwalk 09fd98ec-d55c-29e1-4ae067b0-4aaec0d6.dmp ./symbols

NOTES:

  • symbols can be generated only for application binaries with debug info (Debug or RelWithDebInfo);

  • warn users that dumps may contain sensitive infomatiom;

  • (for wallet binaries) ask users to generate dumps locally instead of sharing raw minidump file publicly.

breakpad repository