crashpad-rs

Rust bindings for Google Crashpad crash reporting system.

Project Structure

Note: The directories are published with different names to avoid conflicts on crates.io:

• crashpad-sys/ → crashpad-rs-sys
• crashpad/ → crashpad-rs

Features

• Cross-platform: macOS, Linux, Windows, iOS, Android
• Safe API: Rust-safe wrapper around Crashpad C++ library
• Flexible Configuration: Runtime handler configuration
• Zero-copy: Minimal overhead for crash reporting
• Production Ready: Battle-tested crash reporting solution

Installation

Add to your Cargo.toml:

[dependencies]
crashpad-rs = "0.1"

Quick Start

use crashpad_rs::{CrashpadClient, CrashpadConfig};
use std::collections::HashMap;

fn main() -> Result<(), Box<dyn std::error::Error>> {
    // Initialize the Crashpad client
    let client = CrashpadClient::new()?;

    // Configure crash reporting
    let config = CrashpadConfig::builder()
        .handler_path("/path/to/crashpad_handler")  // Handler executable
        .database_path("./crashes")                 // Local crash storage
        .url("https://your-crash-server.com/submit") // Upload endpoint
        .build();

    // Add application metadata
    let mut annotations = HashMap::new();
    annotations.insert("version".to_string(), env!("CARGO_PKG_VERSION").to_string());
    annotations.insert("build".to_string(), "release".to_string());

    // Start crash monitoring
    client.start_with_config(&config, &annotations)?;

    // Your application code here
    Ok(())
}

Configuration

Basic Configuration (Local Only)

// Minimal config - crashes saved locally, no upload
let config = CrashpadConfig::builder()
.handler_path("./crashpad_handler")  // Required on desktop platforms
.database_path("./crash_dumps")      // Where to store crash dumps
.build();

Production Configuration

// Full configuration with upload server
let config = CrashpadConfig::builder()
.handler_path(std::env::var("CRASHPAD_HANDLER")
.unwrap_or_else( | _ | "./crashpad_handler".to_string()))
.database_path("/var/crash/myapp")
.metrics_path("/var/metrics/myapp")  // Optional: metrics storage
.url("https://crashes.example.com/api/minidump")
.rate_limit(true)  // Limit upload frequency
.compress_uploads(true)  // Compress before uploading
.build();

Platform-Specific Configuration

Desktop (macOS/Linux/Windows)

// Handler path is required for desktop platforms
let config = CrashpadConfig::builder()
.handler_path("./crashpad_handler")  // Must point to handler executable
.database_path("./crashes")
.build();

iOS/tvOS/watchOS

// iOS uses in-process handler - no handler_path needed
let config = CrashpadConfig::builder()
.database_path("./crashes")  // Relative to app's Documents directory
.url("https://crashes.example.com/api/minidump")
.build();

Android

// Android can use external handler (as .so file in APK)
let config = CrashpadConfig::builder()
.handler_path("./libcrashpad_handler.so")  // Renamed for APK distribution
.database_path("/data/data/com.example.app/crashes")
.build();

Environment-Based Configuration

// Adjust configuration based on environment
let config = if cfg!(debug_assertions) {
// Development: local storage only
CrashpadConfig::builder()
.handler_path("./target/debug/crashpad_handler")
.database_path("./dev_crashes")
.build()
} else {
// Production: with upload server
CrashpadConfig::builder()
.handler_path("/usr/local/bin/crashpad_handler")
.database_path("/var/crash/myapp")
.url("https://crashes.example.com/submit")
.build()
};

Platform Support

Examples

Running the Test Example

1. Build the example and handler

   # Build everything including the handler
   cargo build --example crashpad_test_cli
   
   # The handler will be at: target/debug/crashpad_handler
   # The example will be at: target/debug/examples/crashpad_test_cli
   

2. Run with handler in same directory (easiest)

   # Copy handler to current directory
   cp target/debug/crashpad_handler .
   
   # Run the example (will look for handler in current directory as fallback)
   ./target/debug/examples/crashpad_test_cli
   

3. Run with environment variable

   # Set handler path explicitly
   export CRASHPAD_HANDLER=target/debug/crashpad_handler
   
   # Run from anywhere
   cargo run --example crashpad_test_cli
   

4. Run directly with cargo (if handler is in PATH or current directory)

   # If you have crashpad_handler in current directory or PATH
   cargo run --example crashpad_test_cli
   

Note: The example looks for the handler in this order:

1. Path specified in config (if provided)
2. CRASHPAD_HANDLER environment variable
3. Same directory as the executable (fallback)
4. Current working directory (fallback)

Handler Deployment

The crashpad_handler executable must be available at runtime. Common approaches:

1. Same directory as application (simplest)

   my-app/
   ├── my-app
   └── crashpad_handler
   

2. System path (for installed applications)

   /usr/local/bin/crashpad_handler
   

3. Environment variable (flexible deployment)

   export CRASHPAD_HANDLER=/opt/myapp/bin/crashpad_handler
   

4. Bundled in package (platform-specific)

   • macOS: Inside .app bundle
   • Linux: In AppImage or snap
   • Android: As .so file in APK
   • iOS: Not needed (in-process)

Documentation

For Library Users

• API Documentation - Full API reference
• Integration Guide - Production integration
• Platform Notes - Platform-specific considerations

For Contributors

• Development Guide - Build, test, and contribute
• Architecture - Technical design decisions
• Conventions - Coding standards

Troubleshooting

Handler Not Found

• Verify handler executable exists and has execute permissions
• Check CRASHPAD_HANDLER environment variable
• Explicitly set path in config: .handler_path("/path/to/crashpad_handler")
• Ensure handler architecture matches application

Crashes Not Being Captured

• Confirm handler process is running
• Check database path has write permissions
• Verify network connectivity for uploads

License

Licensed under MIT license (LICENSE).

Contributing

Contributions are welcome! See DEVELOPING.md for build and test instructions.

Support

• Issues: GitHub Issues
• Discussions: GitHub Discussions
• Security: Report security vulnerabilities to security@example.com