A utility to automate analysis of core dumps from crashes during CI builds and test runs.

Support Linux, OSX (somewhat), and Windows. Tested with Appveyor, Github Actions, Travis-CI.

On Linux, uses the corepattern facility to capture, and analyzes with GDB. On OSX, find and print any CrashReporter logs. On Windows, uses the AeDebug facility to capture, and analyzes with CDB.

Usage on Github Actions:

...
jobs:
  test:
    runs-on: ${{ matrix.os }}
    name: My Job
    steps:
      - uses: actions/checkout@v3
      - uses: mdavidsaver/ci-core-dumper@master
      - runs: |
         ulimit -c unlimited
         ... something which might crash

With Github Actions only, a dummy ulimit command is provided on Windows.

Usage in Travis-CI:

install:
  - sudo pip install git+https://github.com/mdavidsaver/ci-core-dumper#egg=ci-core-dumper

before_script:
  - sudo python -m ci_core_dumper install

script:
  - ulimit -c unlimited
  - ... something which might crash

after_failure:
  - python -m ci_core_dumper report

Info on stages.

Usage in Appveyor:

install:
  - cmd: pip install git+https://github.com/mdavidsaver/ci-core-dumper#egg=ci-core-dumper

before_test:
  - cmd: python -m ci_core_dumper install

test_script:
  - ... something which might crash

on_failure:
  - cmd: python -m ci_core_dumper report

Info on stages.

Test crashes should be rare. So the best case is that ci-core-dumper is installed but never used. There is a risk of false negatives if some issue prevents ci-core-dumper from functioning correctly. eg. omitting 'ulimit -c unlimited' on *NIX or SetErrorMode(2) on Windows.

The action arguments extra_cdb: and extra_gdb: can be used to pass a semicolon separated list of extra debugger commands to CDB or GDB. eg.

...
jobs:
...
      - uses: mdavidsaver/ci-core-dumper@master
        with:
          extra_gdb: "info auto-load"

Please report any issue on the Github project.

• Github Project