Fetch translations & Recreate libretro_core_options_intl.h

enable Copy to VRAM for a bunch of games
Worms World Party (US) Hundred Swords Musapey's Choco Marker (dreamcast) Choco Marker (naomi) Sister Princess Premium Edition Sentimental Graffiti 1 & 2 Kanon Aikagi AIR Issue #1265
2026-11-08 01:48:31 -10:00 · 2023-10-27 22:19:54 +00:00 · 2023-10-27 14:56:28 +02:00 · 2023-10-27 14:52:07 +02:00 · 2023-10-25 16:59:01 +02:00 · 2023-10-25 16:53:25 +02:00
4365 changed files with 278356 additions and 1313528 deletions
@@ -1,12 +1,12 @@
 freebsd_instance:
-  image_family: freebsd-13-0
+  image_family: freebsd-13-2

 env:
  CCACHE_DIR: /tmp/ccache
  CIRRUS_CLONE_SUBMODULES: true

 task:
-  install_script: pkg install -y alsa-lib ccache cmake evdev-proto git libao libevdev libudev-devd libzip mesa-libs miniupnpc ninja pkgconf png pulseaudio sdl2
+  install_script: pkg install -y alsa-lib ccache cmake evdev-proto git libao libevdev libudev-devd libzip mesa-libs miniupnpc ninja pkgconf pulseaudio sdl2
  ccache_cache:
    folder: /tmp/ccache
  script:
@@ -1 +1 @@
-custom: ['https://utip.io/flyinghead', 'https://www.paypal.com/paypalme/FlycastEmu']
+custom: ['https://www.paypal.com/paypalme/FlycastEmu']
@@ -10,46 +10,57 @@ jobs:
      - name: Set up build environment
        run: |
          sudo apt-get update
-          sudo apt-get -y install ccache ninja-build
-          echo "CCACHE_DIR=/tmp/ccache" >> $GITHUB_ENV
+          sudo apt-get -y install ccache libcurl4-openssl-dev ninja-build

-      # Workaround for https://github.com/actions/virtual-environments/issues/3078
-      - name: Downgrade CMake
-        uses: jwlawson/[email protected]
-        with:
-          cmake-version: '3.19.x'
-
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
        with:
          fetch-depth: 0
          submodules: true
-
-      - uses: actions/cache@v2
+          
+      - uses: actions/setup-java@v3
        with:
-          path: /tmp/ccache
+          java-version: '17'
+          distribution: 'temurin'
+          cache: 'gradle'
+
+      - uses: actions/cache@v3
+        with:
+          path: ~/.ccache
          key: android-ccache-${{ github.sha }}
          restore-keys: android-ccache-

-      - uses: actions/cache@v2
-        with:
-          path: |
-            ~/.gradle/caches
-            ~/.gradle/wrapper
-          key: android-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }}
-          restore-keys: android-gradle-
-
      - name: Gradle
        working-directory: shell/android-studio
        run: ./gradlew assembleRelease --parallel
+        env:
+          SENTRY_UPLOAD_URL: ${{ secrets.SENTRY_UPLOAD_URL }}

-      - uses: actions/upload-artifact@v2
+      - uses: actions/upload-artifact@v3
        with:
          name: flycast-release.apk
          path: shell/android-studio/flycast/build/outputs/apk/release/flycast-release.apk

+      - name: Build dump_syms
+        working-directory: core/deps/breakpad
+        run: |
+          ./configure --prefix=$PWD
+          make -j2
+          make install
+
+      - name: Extract symbols
+        run: |
+          DUMP_SYMS=./core/deps/breakpad/bin/dump_syms
+          SO_DIR=shell/android-studio/flycast/build/intermediates/merged_native_libs/release/out/lib
+          for arch in arm64-v8a armeabi-v7a x86 x86_64 ; do
+            $DUMP_SYMS $SO_DIR/$arch/libflycast.so > libflycast.so.sym
+            BUILD_ID=`head -1 libflycast.so.sym | awk '{ print $4 }'`
+            mkdir -p symbols/libflycast.so/$BUILD_ID
+            mv libflycast.so.sym symbols/libflycast.so/$BUILD_ID
+          done
+
      - name: Configure AWS Credentials
        id: aws-credentials
-        uses: aws-actions/configure-aws-credentials@v1
+        uses: aws-actions/configure-aws-credentials@v2
        with:
          aws-access-key-id: AKIAJOZQS4H2PHQWYFCA
          aws-secret-access-key: ${{ secrets.S3_SECRET_KEY }}
@@ -60,23 +71,24 @@ jobs:
        run: aws s3 sync shell/android-studio/flycast/build/outputs/apk/release s3://flycast-builds/android/${GITHUB_REF#refs/}-$GITHUB_SHA --acl public-read --exclude='*.json' --follow-symlinks
        if: ${{ steps.aws-credentials.outputs.aws-account-id != '' }}

-      - name: Build dump_syms
-        working-directory: core/deps/breakpad
+      - name: Setup Sentry CLI
+        uses: mathieu-bour/setup-sentry-cli@v1
+        env:
+          SENTRY_TOKEN: ${{ secrets.SENTRY_TOKEN }}
+        with:
+          url: https://sentry.io
+          token: ${{ env.SENTRY_TOKEN }}
+          organization: flycast
+          project: minidump
+        if: ${{ env.SENTRY_TOKEN != '' }}
+      
+      - name: Upload symbols to Sentry
        run: |
-          cmake -B build -DCMAKE_BUILD_TYPE=Release -G Ninja
-          cmake --build build --config Release --target dump_syms
-
-      - name: Extract symbols
-        run: |
-          DUMP_SYMS=./core/deps/breakpad/build/dump_syms
-          SO_DIR=shell/android-studio/flycast/build/intermediates/cmake/release/obj
-          for arch in arm64-v8a armeabi-v7a x86 x86_64 ; do
-            $DUMP_SYMS $SO_DIR/$arch/libflycast.so > libflycast.so.sym
-            BUILD_ID=`head -1 libflycast.so.sym | awk '{ print $4 }'`
-            mkdir -p symbols/libflycast.so/$BUILD_ID
-            mv libflycast.so.sym symbols/libflycast.so/$BUILD_ID
-          done
-
-      - name: Upload to S3 (symbols)
-        run: aws s3 sync symbols s3://flycast-symbols/android --follow-symlinks
-        if: ${{ steps.aws-credentials.outputs.aws-account-id != '' }}
+          VERSION=$(git describe --tags --always)
+          sentry-cli releases new "$VERSION"
+          sentry-cli releases set-commits "$VERSION" --auto
+          sentry-cli debug-files upload symbols
+        shell: bash
+        env:
+          SENTRY_TOKEN: ${{ secrets.SENTRY_TOKEN }}
+        if: ${{ env.SENTRY_TOKEN != '' }}
@@ -7,147 +7,144 @@ jobs:
    name: ${{ matrix.config.name }}
    runs-on: ${{ matrix.config.os }}

+    defaults:
+      run:
+        shell: ${{ matrix.config.shell }}
+
+    env:
+      CCACHE_DIR: ${{ github.workspace }}/.ccache
+
    strategy:
      matrix:
        config:
-          - {name: i686-pc-windows-msvc, os: windows-latest, cmakeArgs: -DCMAKE_SYSTEM_VERSION="10.0.18362.0" -G "Visual Studio 16 2019" -A Win32, buildType: Release}
-          - {name: apple-darwin, os: macos-latest, cmakeArgs: -G "Xcode", destDir: osx, buildType: Release}
-          - {name: apple-ios, os: macos-latest, cmakeArgs: -DCMAKE_SYSTEM_NAME=iOS -G "Xcode", destDir: ios, buildType: Release}
-          - {name: x86_64-pc-linux-gnu, os: ubuntu-latest, buildType: Release}
-          - {name: x86_64-pc-windows-msvc, os: windows-latest, cmakeArgs: -DCMAKE_SYSTEM_VERSION="10.0.18362.0" -G "Visual Studio 16 2019" -A x64, buildType: Release}
-          - {name: x86_64-w64-mingw32, os: windows-latest, cmakeArgs: -G "MinGW Makefiles", destDir: win, buildType: RelWithDebInfo}
-          - {name: libretro-x86_64-pc-linux-gnu, os: ubuntu-latest, cmakeArgs: -DLIBRETRO=ON -DCMAKE_POSITION_INDEPENDENT_CODE=TRUE, buildType: Release}
-          - {name: libretro-x86_64-w64-mingw32, os: windows-latest, cmakeArgs: -DLIBRETRO=ON -G "MinGW Makefiles", buildType: Release}
+          - {name: i686-pc-windows-msvc, os: windows-latest, shell: cmd, arch: x86, cmakeArgs: -G Ninja, buildType: Release}
+          - {name: apple-darwin, os: macos-latest, shell: sh, cmakeArgs: -G Xcode -DAPPLE_BREAKPAD=ON, destDir: osx, buildType: RelWithDebInfo}
+          - {name: apple-ios, os: macos-latest, shell: sh, cmakeArgs: -DCMAKE_SYSTEM_NAME=iOS -G Xcode, destDir: ios, buildType: Release}
+          - {name: x86_64-pc-linux-gnu, os: ubuntu-20.04, shell: sh, cmakeArgs: -G Ninja, destDir: linux, buildType: RelWithDebInfo}
+          - {name: x86_64-pc-windows-msvc, os: windows-latest, shell: cmd, arch: x64, cmakeArgs: -G Ninja, buildType: Release}
+          - {name: x86_64-w64-mingw32, os: windows-latest, shell: 'msys2 {0}', cmakeArgs: -G Ninja, destDir: win, buildType: RelWithDebInfo}
+          - {name: libretro-x86_64-pc-linux-gnu, os: ubuntu-latest, shell: sh, cmakeArgs: -DLIBRETRO=ON -DCMAKE_POSITION_INDEPENDENT_CODE=TRUE -G Ninja, buildType: Release}
+          - {name: libretro-x86_64-w64-mingw32, os: windows-latest, shell: 'msys2 {0}', cmakeArgs: -DLIBRETRO=ON -G Ninja, buildType: Release}

    steps:
-      - name: Set up build environment (macos-latest)
+      - name: Set up build environment (macOS)
        run: |
-          brew install ccache libao libomp pulseaudio zlib ldid
-          echo "/usr/local/opt/ccache/libexec" >> $GITHUB_PATH
-          echo "CCACHE_DIR=/tmp/ccache" >> $GITHUB_ENV
-        if: matrix.config.os == 'macos-latest'
+          # Unlink and re-link to prevent errors when github mac runner images install python outside of brew. See https://github.com/actions/setup-python/issues/577
+          brew list -1 | grep python | while read formula; do brew unlink $formula; brew link --overwrite $formula; done
+          brew update || :
+          brew install libao ldid ninja pulseaudio
+          VULKAN_VER=1.3.261.1 && aria2c https://sdk.lunarg.com/sdk/download/$VULKAN_VER/mac/vulkansdk-macos-$VULKAN_VER.dmg
+          hdiutil attach ./vulkansdk-macos-*.dmg -mountpoint /Volumes/VulkanSDK
+          sudo /Volumes/VulkanSDK/InstallVulkan.app/Contents/MacOS/InstallVulkan --root $HOME/VulkanSDK --accept-licenses --default-answer --confirm-command install
+          hdiutil detach /Volumes/VulkanSDK
+          echo "VULKAN_SDK=$HOME/VulkanSDK/macOS" >> $GITHUB_ENV
+        if: runner.os == 'macOS'

-      - name: Set up build environment (ubuntu-latest)
+      - name: Set up build environment (Linux)
        run: |
+          sudo add-apt-repository ppa:christianrauch/libdecoration
          sudo apt-get update
-          sudo apt-get -y install ccache libao-dev libasound2-dev libevdev-dev libgl1-mesa-dev libpulse-dev libsdl2-dev libudev-dev libzip-dev libminiupnpc-dev
-          echo "CCACHE_DIR=/tmp/ccache" >> $GITHUB_ENV
-        if: matrix.config.os == 'ubuntu-latest'
+          sudo apt-get -y install ccache libao-dev libasound2-dev libevdev-dev libgl1-mesa-dev liblua5.3-dev libminiupnpc-dev libpulse-dev libsdl2-dev libudev-dev libzip-dev ninja-build libcurl4-openssl-dev
+          sudo apt-get -y install libwayland-dev libdecor-0-dev libaudio-dev libjack-dev libsndio-dev libsamplerate0-dev libx11-dev libxext-dev libxrandr-dev libxcursor-dev libxfixes-dev libxi-dev libxss-dev libxkbcommon-dev libdrm-dev libgbm-dev libgles2-mesa-dev libegl1-mesa-dev libdbus-1-dev libibus-1.0-dev libudev-dev fcitx-libs-dev
+        if: runner.os == 'Linux'

-      - name: Set up build environment (windows-latest)
-        run: echo "DXSDK_DIR=${Env:HOMEDRIVE}${Env:HOMEPATH}\ccache\" | Out-File -FilePath $Env:GITHUB_ENV -Encoding utf-8 -Append
-        if: matrix.config.os == 'windows-latest' && matrix.config.name != 'libretro-x86_64-w64-mingw32'
-
-      - uses: actions/cache@v2
-        with:
-          path: /tmp/ccache
-          key: ccache-${{ matrix.config.os }}-${{ github.sha }}
-          restore-keys: ccache-${{ matrix.config.os }}-
-        if: matrix.config.os != 'windows-latest'
-
-      - uses: actions/cache@v2
-        id: cache
-        with:
-          path: $HOME/ccache
-          key: ccache-${{ matrix.config.os }}-${{ github.sha }}
-          restore-keys: ccache-${{ matrix.config.os }}-
-        if: matrix.config.os == 'windows-latest'
-
-      - name: Download DX2010
-        if: matrix.config.os == 'windows-latest' && matrix.config.name != 'libretro-x86_64-w64-mingw32'
-        run:   |
-               curl -L https://download.microsoft.com/download/a/e/7/ae743f1f-632b-4809-87a9-aa1bb3458e31/DXSDK_Jun10.exe -o _DX2010_.exe
-               7z x _DX2010_.exe DXSDK/Include -o_DX2010_
-               7z x _DX2010_.exe DXSDK/Lib/x86 -o_DX2010_
-               7z x _DX2010_.exe DXSDK/Lib/x64 -o_DX2010_
-               mv _DX2010_/DXSDK $HOME/ccache
-               rm -fR _DX*_ _DX*_.exe
-        shell: bash
-
-      - name: Install MSYS2
+      - name: Set up build environment (Windows, MinGW)
        uses: msys2/setup-msys2@v2
        with:
          msystem: MINGW64
-          install: git base-devel mingw-w64-x86_64-toolchain mingw-w64-x86_64-cmake mingw-w64-x86_64-breakpad-git
-        if: matrix.config.os == 'windows-latest'
+          install: git make mingw-w64-x86_64-ccache mingw-w64-x86_64-cmake mingw-w64-x86_64-lua mingw-w64-x86_64-ninja mingw-w64-x86_64-SDL2 mingw-w64-x86_64-toolchain
+        if: matrix.config.shell == 'msys2 {0}'

-      - name: Downgrade gcc to 10.3
+      - name: Set up build environment (Windows, Visual Studio)
        run: |
-          pacman -U --noconfirm https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-gcc-libs-10.3.0-8-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-gcc-10.3.0-8-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-gcc-ada-10.3.0-8-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-gcc-fortran-10.3.0-8-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-gcc-libgfortran-10.3.0-8-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-gcc-objc-10.3.0-8-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-libgccjit-10.3.0-8-any.pkg.tar.zst
-          pacman -U --noconfirm https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-crt-git-9.0.0.6246.ae63cde27-1-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-headers-git-9.0.0.6246.ae63cde27-1-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-libmangle-git-9.0.0.6246.ae63cde27-1-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-libwinpthread-git-9.0.0.6246.ae63cde27-1-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-tools-git-9.0.0.6246.ae63cde27-1-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-winpthreads-git-9.0.0.6246.ae63cde27-1-any.pkg.tar.zst https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-winstorecompat-git-9.0.0.6246.ae63cde27-1-any.pkg.tar.zst
-          pacman -U --noconfirm https://repo.msys2.org/mingw/mingw64/mingw-w64-x86_64-cmake-3.20.5-2-any.pkg.tar.zst
-        shell: msys2 {0}
-        if: matrix.config.os == 'windows-latest'
+          choco install ccache directx-sdk ninja
+          echo DXSDK_DIR=C:\Program Files (x86)\Microsoft DirectX SDK (June 2010)>> %GITHUB_ENV%
+        if: matrix.config.shell == 'cmd'

-      - uses: actions/checkout@v2
+      - uses: ilammy/msvc-dev-cmd@v1
+        with:
+          arch: ${{ matrix.config.arch }}
+        if: matrix.config.shell == 'cmd'
+
+      - uses: actions/checkout@v3
        with:
          fetch-depth: 0
          submodules: true

-      - name: Create artifact directory
-        run: mkdir -p build/artifact
-
-      - name: Build SDL (macos)
-        run: |
-          cd shell/apple
-          mkdir artifacts
-          brew install --build-from-source ./sdl2.rb
+      - name: Compile a universal OpenMP (macOS)
+        run: HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK=1 brew reinstall --build-from-source --formula ./shell/apple/libomp.rb
        if: matrix.config.name == 'apple-darwin'

+      - name: Compile OpenMP.xcframework (iOS)
+        run: ./shell/apple/emulator-ios/OpenMP/build_ios_openmp.sh --disableSimulator
+        if: matrix.config.name == 'apple-ios'
+
+      - uses: actions/cache@v3
+        with:
+          path: ${{ env.CCACHE_DIR }}
+          key: ccache-${{ matrix.config.name }}-${{ github.sha }}
+          restore-keys: ccache-${{ matrix.config.name }}-
+        if: runner.os != 'macOS'
+
      - name: CMake
        run: |
-          cmake -B build -DCMAKE_BUILD_TYPE=${{ matrix.config.buildType }} -DCMAKE_RUNTIME_OUTPUT_DIRECTORY_RELEASE=artifact -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=artifact ${{ matrix.config.cmakeArgs }}
-          cmake --build build --config Release --parallel 2
-        if: matrix.config.os != 'windows-latest'
-
-      - name: CMake (windows)
-        shell: msys2 {0}
-        run: |
-          unset temp tmp
-          cmake -B build -DCMAKE_BUILD_TYPE=${{ matrix.config.buildType }} -DCMAKE_RUNTIME_OUTPUT_DIRECTORY_RELEASE=artifact -DCMAKE_RUNTIME_OUTPUT_DIRECTORY_RELWITHDEBINFO=artifact -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=artifact ${{ matrix.config.cmakeArgs }}
-          cmake --build build --config Release --parallel 2
-        if: matrix.config.os == 'windows-latest'
+          cmake -B build -DCMAKE_BUILD_TYPE=${{ matrix.config.buildType }} -DCMAKE_INSTALL_PREFIX=artifact ${{ matrix.config.cmakeArgs }} -DSENTRY_UPLOAD_URL=${{ env.SENTRY_UPLOAD_URL }}
+          cmake --build build --config ${{ matrix.config.buildType }} --target install
+        env:
+          SENTRY_UPLOAD_URL: ${{ secrets.SENTRY_UPLOAD_URL }}

      - name: Unit Tests
        run: |
-          mkdir -p build/tests
-          cmake -B build -DCMAKE_BUILD_TYPE=${{ matrix.config.buildType }} -DCMAKE_RUNTIME_OUTPUT_DIRECTORY_RELEASE=tests -DENABLE_CTEST=ON ${{ matrix.config.cmakeArgs }}
-          cmake --build build --config Release --parallel 2
-          ./build/tests/flycast
+          cmake -B build -DCMAKE_BUILD_TYPE=${{ matrix.config.buildType }} -DCMAKE_INSTALL_PREFIX=artifact -DENABLE_CTEST=ON ${{ matrix.config.cmakeArgs }}
+          cmake --build build --config ${{ matrix.config.buildType }}
+          ./build/flycast
        if: matrix.config.name == 'x86_64-pc-linux-gnu'

      - name: Dump symbols
-        shell: msys2 {0}
        run: |
-          dump_syms build/artifact/flycast.exe > flycast.exe.sym 2>/dev/null
-          BUILD_ID=`head -1 flycast.exe.sym | awk '{ print $4 }'`
-          mkdir -p symbols/flycast.exe/$BUILD_ID
-          mv flycast.exe.sym symbols/flycast.exe/$BUILD_ID
-          strip build/artifact/flycast.exe
+          mkdir -p symbols
+          core/deps/breakpad/bin/dump_syms artifact/bin/flycast.exe > symbols/flycast.sym 2>/dev/null
+          strip artifact/bin/flycast.exe
        if: matrix.config.name == 'x86_64-w64-mingw32'

-      - uses: actions/upload-artifact@v2
+      - name: Build breakpad (linux)
+        working-directory: core/deps/breakpad
+        run: |
+          ./configure
+          make
+          sudo make install
+        if: matrix.config.name == 'x86_64-pc-linux-gnu'
+
+      - name: Dump symbols and make AppImage (linux)
+        run: |
+          mkdir -p symbols
+          dump_syms artifact/bin/flycast > symbols/flycast.sym 2>/dev/null
+          strip artifact/bin/flycast
+          shell/linux/make-appimage.sh . artifact/bin appimage
+          mv flycast-x86_64.AppImage artifact/bin
+          rm artifact/bin/flycast
+        if: matrix.config.name == 'x86_64-pc-linux-gnu'
+
+      - uses: actions/upload-artifact@v3
        with:
          name: flycast-${{ matrix.config.name }}
-          path: build/artifact
+          path: artifact/bin

      - name: Package app (macos)
        run: |
-          cd build/artifact
-          rm -rf Flycast.swiftmodule
-          zip -r flycast.app.zip Flycast.app
-          rm -rf Flycast.app
+          cd artifact/bin
+          zip -rm flycast.app.zip Flycast.app
        if: matrix.config.name == 'apple-darwin'

      - name: Package app (windows)
        run: |
-          powershell Compress-Archive build/artifact/flycast.exe build/artifact/flycast.zip 
-          rm build/artifact/flycast.exe
+          powershell Compress-Archive artifact/bin/flycast.exe artifact/bin/flycast.zip 
+          rm artifact/bin/flycast.exe
        if: matrix.config.name == 'x86_64-w64-mingw32'

      - name: Configure AWS Credentials
        id: aws-credentials
-        uses: aws-actions/configure-aws-credentials@v1
+        uses: aws-actions/configure-aws-credentials@v2
        with:
          aws-access-key-id: AKIAJOZQS4H2PHQWYFCA
          aws-secret-access-key: ${{ secrets.S3_SECRET_KEY }}
@@ -155,11 +152,29 @@ jobs:
        if: github.repository == 'flyinghead/flycast' && github.event_name == 'push' && matrix.config.destDir != ''

      - name: Upload to S3
-        run: aws s3 sync build/artifact s3://flycast-builds/${{ matrix.config.destDir }}/${GITHUB_REF#refs/}-$GITHUB_SHA --acl public-read --follow-symlinks
+        run: aws s3 sync artifact/bin s3://flycast-builds/${{ matrix.config.destDir }}/${GITHUB_REF#refs/}-$GITHUB_SHA --acl public-read --follow-symlinks
        shell: bash
        if: ${{ steps.aws-credentials.outputs.aws-account-id != '' }}

-      - name: Upload symbols to S3
-        run: aws s3 sync symbols s3://flycast-symbols/${{ matrix.config.destDir }} --follow-symlinks
-        if: ${{ steps.aws-credentials.outputs.aws-account-id != '' && matrix.config.os == 'windows-latest' }}
-        
+      - name: Setup Sentry CLI
+        uses: mathieu-bour/setup-sentry-cli@v1
+        env:
+          SENTRY_TOKEN: ${{ secrets.SENTRY_TOKEN }}
+        with:
+          url: https://sentry.io
+          token: ${{ env.SENTRY_TOKEN }}
+          organization: flycast
+          project: minidump
+        if: ${{ env.SENTRY_TOKEN != '' }}
+      
+      - name: Upload symbols to Sentry (Windows, macOS, Linux)
+        run: |
+          VERSION=$(git describe --tags --always)
+          sentry-cli releases new "$VERSION"
+          sentry-cli releases set-commits "$VERSION" --auto
+          sentry-cli debug-files upload symbols
+        shell: bash
+        env:
+          SENTRY_TOKEN: ${{ secrets.SENTRY_TOKEN }}
+        if: ${{ env.SENTRY_TOKEN != '' && (matrix.config.name == 'x86_64-w64-mingw32' || matrix.config.name == 'apple-darwin' || matrix.config.name == 'x86_64-pc-linux-gnu') }}
+        
@@ -15,15 +15,18 @@ jobs:
    runs-on: ubuntu-latest
    steps:
      - name: Setup Java JDK
-        uses: actions/setup-java@v1
+        uses: actions/setup-java@v3
        with:
-          java-version: 1.8
+          java-version: 18
+          distribution: zulu

      - name: Setup Python
-        uses: actions/setup-python@v2
+        uses: actions/setup-python@v4
+        with:
+          python-version: '3.10'

      - name: Checkout
-        uses: actions/checkout@v2
+        uses: actions/checkout@v3

      - name: Upload Source
        shell: bash
@@ -12,15 +12,18 @@ jobs:
    runs-on: ubuntu-latest
    steps:
      - name: Setup Java JDK
-        uses: actions/setup-java@v1
+        uses: actions/setup-java@v3
        with:
-          java-version: 1.8
+          java-version: 18
+          distribution: zulu

      - name: Setup Python
-        uses: actions/setup-python@v2
+        uses: actions/setup-python@v4
+        with:
+          python-version: '3.10'

      - name: Checkout
-        uses: actions/checkout@v2
+        uses: actions/checkout@v3
        with:
          persist-credentials: false # otherwise, the token used is the GITHUB_TOKEN, instead of your personal access token.
          fetch-depth: 0 # otherwise, there would be errors pushing refs to the destination repository.
@@ -6,48 +6,48 @@ jobs:
  build:
    name: ${{ matrix.config.name }}
    runs-on: ubuntu-latest
-    container: devkitpro/devkita64:latest
+    container: devkitpro/devkita64:20220128

    strategy:
      matrix:
        config:
          - {name: standalone, destDir: switch}
-          - {name: libretro, cmakeArgs: -DCMAKE_ARCHIVE_OUTPUT_DIRECTORY=artifact -DLIBRETRO=ON}
+          - {name: libretro, cmakeArgs: -DLIBRETRO=ON}

    steps:
      - name: Set up build environment
        run: |
          sudo apt-get update
-          sudo apt-get -y install awscli ninja-build
+          sudo apt-get -y install awscli ccache ninja-build

-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
        with:
          fetch-depth: 0
          submodules: true

+      - uses: actions/cache@v3
+        with:
+          path: ~/.ccache
+          key: ccache-switch-${{ matrix.config.name }}-${{ github.sha }}
+          restore-keys: ccache-switch-${{ matrix.config.name }}-
+
      - name: CMake
        run: |
-          $DEVKITPRO/portlibs/switch/bin/aarch64-none-elf-cmake -B build -DCMAKE_BUILD_TYPE=Release -G Ninja ${{ matrix.config.cmakeArgs }}
-          cmake --build build --config Release
+          $DEVKITPRO/portlibs/switch/bin/aarch64-none-elf-cmake -B build -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=artifact -G Ninja ${{ matrix.config.cmakeArgs }}
+          cmake --build build --config Release --target install

-      - name: Prepare upload
-        run: |
-          mkdir build/artifact
-          mv build/flycast.nro build/artifact/flycast.nro
-        if: hashFiles('build/flycast.nro') != ''
-
-      - uses: actions/upload-artifact@v2
+      - uses: actions/upload-artifact@v3
        with:
          name: flycast-switch-${{ matrix.config.name }}
-          path: build/artifact
+          path: artifact/bin

      - name: Package app
-        run: zip -m build/artifact/flycast.nro.zip build/artifact/flycast.nro
-        if: hashFiles('build/artifact/flycast.nro') != ''
+        run: zip -m artifact/bin/flycast.nro.zip artifact/bin/flycast.nro
+        if: hashFiles('artifact/bin/flycast.nro') != ''

      - name: Configure AWS Credentials
        id: aws-credentials
-        uses: aws-actions/configure-aws-credentials@v1
+        uses: aws-actions/configure-aws-credentials@v2
        with:
          aws-access-key-id: AKIAJOZQS4H2PHQWYFCA
          aws-secret-access-key: ${{ secrets.S3_SECRET_KEY }}
@@ -55,5 +55,5 @@ jobs:
        if: github.repository == 'flyinghead/flycast' && github.event_name == 'push' && matrix.config.destDir != ''

      - name: Upload to S3
-        run: aws s3 sync build/artifact s3://flycast-builds/${{ matrix.config.destDir }}/${GITHUB_REF#refs/}-$GITHUB_SHA --acl public-read --follow-symlinks
+        run: aws s3 sync artifact/bin s3://flycast-builds/${{ matrix.config.destDir }}/${GITHUB_REF#refs/}-$GITHUB_SHA --acl public-read --follow-symlinks
        if: ${{ steps.aws-credentials.outputs.aws-account-id != '' }}
@@ -0,0 +1,69 @@
+name: Windows UWP CI
+
+on: [push, pull_request]
+
+jobs:
+  build:
+    runs-on: windows-latest
+
+    env:
+      VCPKG_ROOT: ${{ github.workspace }}/vcpkg
+      VCPKG_DEFAULT_BINARY_CACHE: ${{ github.workspace }}/vcpkg/bincache
+
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+          submodules: true
+
+      - name: bootstrap vcpkg
+        run: |
+          git clone https://github.com/microsoft/vcpkg
+          mkdir vcpkg\bincache
+          vcpkg\bootstrap-vcpkg.bat
+
+      - uses: actions/cache@v3
+        with:
+          path: ${{ env.VCPKG_DEFAULT_BINARY_CACHE }}
+          key: vcpkg-${{ hashFiles( 'vcpkg.json' ) }}
+
+      - name: CMake
+        run: |
+          cmake -B build -DCMAKE_BUILD_TYPE=Release -G "Visual Studio 17 2022" -A x64 -DCMAKE_SYSTEM_NAME=WindowsStore -DCMAKE_SYSTEM_VERSION=10.0.22000.0 -DCMAKE_TOOLCHAIN_FILE=%VCPKG_ROOT%\scripts\buildsystems\vcpkg.cmake
+          cmake --build build --config Release --parallel 2
+        shell: cmd
+
+      - uses: ilammy/msvc-dev-cmd@v1
+
+      - name: Package app
+        run: |
+          mkdir build\artifact
+          cd build\AppPackages\flycast\flycast_*_x64_Test
+          mkdir tmp
+          ren *.msix flycast.msix
+          makeappx.exe unpack /p .\flycast.msix /d tmp
+          copy ..\..\..\Release\*.dll tmp
+          makeappx pack /d tmp /p ..\..\..\artifact\flycast.appx
+
+      - name: Sign app
+        run: signtool sign /f shell\uwp\sign_cert.pfx /p '${{ secrets.SIGN_CERT_PWD }}' /v /fd SHA256 build\artifact\flycast.appx
+        if: github.repository == 'flyinghead/flycast' && github.event_name == 'push'
+
+      - uses: actions/upload-artifact@v3
+        with:
+          name: flycast-uwp
+          path: build/artifact
+
+      - name: Configure AWS Credentials
+        id: aws-credentials
+        uses: aws-actions/configure-aws-credentials@v2
+        with:
+          aws-access-key-id: AKIAJOZQS4H2PHQWYFCA
+          aws-secret-access-key: ${{ secrets.S3_SECRET_KEY }}
+          aws-region: us-east-2
+        if: github.repository == 'flyinghead/flycast' && github.event_name == 'push'
+
+      - name: Upload to S3
+        run: aws s3 sync build/artifact s3://flycast-builds/xbox/${GITHUB_REF#refs/}-$GITHUB_SHA --acl public-read --follow-symlinks
+        shell: bash
+        if: ${{ steps.aws-credentials.outputs.aws-account-id != '' }}
@@ -1,12 +1,19 @@
 build/
+artifact/

 # macOS
 .DS_Store
+shell/apple/emulator-ios/OpenMP/OpenMP.xcframework

 # Visual Studio
 .vs/
+.vscode/
 out/

 # JetBrains IDES
 .idea/
 cmake-build-*/
+
+# Dependencies from .gitmodules
+core/deps/breakpad/
+core/deps/glslang/
@@ -17,11 +17,22 @@
    CORE_ARGS: -DLIBRETRO=ON -DCMAKE_POSITION_INDEPENDENT_CODE=TRUE -DCMAKE_BUILD_TYPE=Release

 .core-defs-osx-x64:
+  extends: .core-defs
+  variables:
+    CORE_ARGS: -DLIBRETRO=ON -G Xcode -DCMAKE_BUILD_TYPE=Release -DCMAKE_OSX_ARCHITECTURES=x86_64
+    EXTRA_PATH: Release
+
+.core-defs-osx-arm64:
  extends: .core-defs
  variables:
    CORE_ARGS: -DLIBRETRO=ON -G Xcode -DCMAKE_BUILD_TYPE=Release
    EXTRA_PATH: Release

+.core-defs-ios-arm64:
+  extends: .core-defs
+  variables:
+    CORE_ARGS: -DLIBRETRO=ON -DCMAKE_BUILD_TYPE=Release
+
 .core-defs-android:
  extends: .core-defs
  script:
@@ -43,6 +54,10 @@ include:
  - project: 'libretro-infrastructure/ci-templates'
    file: 'osx-cmake-x86.yml'

+  # MacOS arm64
+  - project: 'libretro-infrastructure/ci-templates'
+    file: 'osx-cmake-arm64.yml'
+
  # Linux
  - project: 'libretro-infrastructure/ci-templates'
    file: '/linux-cmake.yml'
@@ -52,10 +67,24 @@ include:
  - project: 'libretro-infrastructure/ci-templates'
    file: '/android-cmake.yml'

+  # iOS arm64
+  - project: 'libretro-infrastructure/ci-templates'
+    file: '/ios-cmake.yml'
+
+  ################################## CONSOLES ################################  
+  # Nintendo Switch
+#  - project: 'libretro-infrastructure/ci-templates'
+#    file: '/libnx-static.yml'
+
+  # tvOS arm64
+  - project: 'libretro-infrastructure/ci-templates'
+    file: '/tvos-cmake.yml'
+
 # Stages for building
 stages:
  - build-prepare
  - build-shared
+#  - build-static

 ##############################################################################
 #################################### STAGES ##################################
@@ -92,6 +121,12 @@ libretro-build-osx-x64:
    - .libretro-osx-cmake-x86
    - .core-defs-osx-x64

+# MacOS arm 64-bit
+libretro-build-osx-arm64:
+  extends:
+    - .libretro-osx-cmake-arm64
+    - .core-defs-osx-arm64
+
 ################################### CELLULAR #################################
 # Android ARMv7a
 android-armeabi-v7a:
@@ -116,3 +151,21 @@ android-x86:
  extends:
    - .libretro-android-cmake-x86
    - .core-defs-android
+
+libretro-build-ios-arm64:
+  extends:
+    - .libretro-ios-cmake-arm64
+    - .core-defs-ios-arm64
+
+################################### CONSOLES #################################
+# Nintendo Switch
+#libretro-build-libnx-aarch64:
+#  extends:
+#    - .libretro-libnx-static-retroarch-master
+#    - .core-defs
+
+# tvOS arm64
+libretro-build-tvos-arm64:
+  extends:
+    - .libretro-tvos-cmake-arm64
+    - .core-defs-ios-arm64
@@ -3,4 +3,28 @@
 	url = https://github.com/libsdl-org/SDL.git
 [submodule "core/deps/libchdr"]
 	path = core/deps/libchdr
-	url = https://github.com/rtissera/libchdr.git
+	url = https://github.com/flyinghead/libchdr.git
+[submodule "core/deps/luabridge"]
+	path = core/deps/luabridge
+	url = https://github.com/vinniefalco/LuaBridge.git
+[submodule "core/deps/breakpad"]
+	path = core/deps/breakpad
+	url = https://github.com/flyinghead/mingw-breakpad
+[submodule "core/deps/Vulkan-Headers"]
+	path = core/deps/Vulkan-Headers
+	url = https://github.com/KhronosGroup/Vulkan-Headers.git
+[submodule "core/deps/VulkanMemoryAllocator"]
+	path = core/deps/VulkanMemoryAllocator
+	url = https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator.git
+[submodule "core/deps/glslang"]
+	path = core/deps/glslang
+	url = https://github.com/KhronosGroup/glslang.git
+[submodule "core/deps/oboe"]
+	path = core/deps/oboe
+	url = https://github.com/google/oboe.git
+[submodule "core/deps/Syphon"]
+	path = core/deps/Syphon
+	url=https://github.com/vkedwardli/Syphon-Framework.git
+[submodule "core/deps/Spout"]
+	path = core/deps/Spout
+	url = https://github.com/vkedwardli/Spout2.git
@@ -3,10 +3,11 @@
 [![Android CI](https://github.com/flyinghead/flycast/actions/workflows/android.yml/badge.svg)](https://github.com/flyinghead/flycast/actions/workflows/android.yml)
 [![C/C++ CI](https://github.com/flyinghead/flycast/actions/workflows/c-cpp.yml/badge.svg)](https://github.com/flyinghead/flycast/actions/workflows/c-cpp.yml)
 [![Nintendo Switch CI](https://github.com/flyinghead/flycast/actions/workflows/switch.yml/badge.svg)](https://github.com/flyinghead/flycast/actions/workflows/switch.yml)
+[![Windows UWP CI](https://github.com/flyinghead/flycast/actions/workflows/uwp.yml/badge.svg)](https://github.com/flyinghead/flycast/actions/workflows/uwp.yml)

 ![flycast logo](https://github.com/flyinghead/flycast/raw/master/shell/linux/flycast.png)

-**Flycast** is a multi-platform Sega Dreamcast, Naomi and Atomiswave emulator derived from [**reicast**](https://reicast.com/).
+**Flycast** is a multi-platform Sega Dreamcast, Naomi, Naomi 2, and Atomiswave emulator derived from [**reicast**](https://github.com/skmp/reicast-emulator).

 Information about configuration and supported features can be found on [**TheArcadeStriker's flycast wiki**](https://github.com/TheArcadeStriker/flycast-wiki/wiki).

@@ -14,24 +15,45 @@ Join us on our [**Discord server**](https://discord.gg/X8YWP8w) for a chat.

 ## Install

-### Flatpak
+### Flatpak (Linux ![ubuntu logo](https://flyinghead.github.io/flycast-builds/ubuntu.png))

-1. [Set up Flatpak](https://www.flatpak.org/setup/)
+1. [Set up Flatpak](https://www.flatpak.org/setup/).

-2. Install Flycast from [Flathub](https://flathub.org/apps/details/org.flycast.Flycast)
+2. Install Flycast from [Flathub](https://flathub.org/apps/details/org.flycast.Flycast):

 `flatpak install -y org.flycast.Flycast`

-3. Run Flycast
+3. Run Flycast:

 `flatpak run org.flycast.Flycast`

-### Binaries
+### Homebrew (MacOS ![apple logo](https://flyinghead.github.io/flycast-builds/apple.png))

-Get fresh builds for your system [on the builds page](https://flyinghead.github.io/flycast-builds/).
+1. [Set up Homebrew](https://brew.sh).

-**New:** Now automated test results are available as well.
+2. Install Flycast via Homebrew:

-## Disclaimer
+`brew install --cask flycast`

-All code contributed to this fork is *not* bound by the Individual Contributor License Agreement of the upstream repository (https://github.com/reicast/reicast-emulator) and shall *not* be considered as a contribution to the upstream repository.
+### Xbox One/Series ![xbox logo](https://flyinghead.github.io/flycast-builds/xbox.png)
+
+Grab the latest build from [**the builds page**](https://flyinghead.github.io/flycast-builds/), or the [**GitHub Actions**](https://github.com/flyinghead/flycast/actions/workflows/uwp.yml). Then install it using the **Xbox Device Portal**.
+
+### Binaries ![android](https://flyinghead.github.io/flycast-builds/android.jpg) ![windows](https://flyinghead.github.io/flycast-builds/windows.png) ![linux](https://flyinghead.github.io/flycast-builds/ubuntu.png) ![apple](https://flyinghead.github.io/flycast-builds/apple.png) ![switch](https://flyinghead.github.io/flycast-builds/switch.png) ![xbox](https://flyinghead.github.io/flycast-builds/xbox.png)
+
+Get fresh builds for your system [**on the builds page**](https://flyinghead.github.io/flycast-builds/).
+
+**New:** Now automated test results are available as well. 
+
+### Build instructions:
+`git clone https://github.com/flyinghead/flycast.git`
+
+`cd flycast`
+
+`git submodule update --init --recursive`
+
+`mkdir build && cd build`
+
+`cmake ..`
+
+`make`
@@ -7,11 +7,10 @@ Here lies the core of our codebase. Everything that's OS inspecific rests here.
 ### Some rudimentary categories are:
 - hw				  -- DC Hardware Components Implementation
 - nullDC.cpp	-- Main entry points
- khronos			-- OpenGL and Vulkan headers
 - oslib				-- Audio drivers
 - cfg				  -- Configuration backend structure
 - reios				-- (Our) Implementation of the DreamCast BIOS
 - deps				-- External dependencies
 - imgread			-- Content drivers
 - rec-*				-- Recompilers
- rend				-- OpenGL and Vulkan renderers
+- rend				-- Graphics renderers and UI
@@ -23,30 +23,20 @@
 #include "deps/lzma/7zCrc.h"
 #include "deps/lzma/Alloc.h"

+#include <cstring>
+
 #define kInputBufSize ((size_t)1 << 18)

 static bool crc_tables_generated;

-bool SzArchive::Open(const char* path)
+bool SzArchive::Open(FILE *file)
 {
 	SzArEx_Init(&szarchive);

 	File_Close(&archiveStream.file);
 	File_Construct(&archiveStream.file);
-#ifdef USE_WINDOWS_FILE
-	nowide::wstackstring wpath;
-	if (!wpath.convert(path))
-		return false;
-	archiveStream.file.handle = CreateFileW(wpath.c_str(),
-			GENERIC_READ, FILE_SHARE_READ, NULL,
-			OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);
-	if (archiveStream.file.handle == INVALID_HANDLE_VALUE)
-		return false;
-#else
-	archiveStream.file.file = nowide::fopen(path, "rb");
-	if (archiveStream.file.file == nullptr)
-		return false;
-#endif
+	archiveStream.file.file = file;
+
 	FileInStream_CreateVTable(&archiveStream);
 	LookToRead2_CreateVTable(&lookStream, 0);
 	lookStream.buf = (Byte *)ISzAlloc_Alloc(&g_Alloc, kInputBufSize);
@@ -25,6 +25,7 @@
 #include "deps/lzma/7zFile.h"

 #include <algorithm>
+#include <cstring>

 class SzArchive : public Archive
 {
@@ -38,9 +39,10 @@ public:
 	ArchiveFile* OpenFile(const char* name) override;
 	ArchiveFile *OpenFileByCrc(u32 crc) override;

-private:
-	bool Open(const char* path) override;
+protected:
+	bool Open(FILE *file) override;

+private:
 	CSzArEx szarchive;
 	UInt32 block_idx;				/* it can have any value before first call (if outBuffer = 0) */
 	Byte *out_buffer;				/* it must be 0 before first call for each new archive. */
@@ -25,11 +25,8 @@ ZipArchive::~ZipArchive()
 	zip_close(zip);
 }

-bool ZipArchive::Open(const char* path)
+bool ZipArchive::Open(FILE *file)
 {
-	FILE *file = nowide::fopen(path, "rb");
-	if (file == nullptr)
-		return false;
 	zip_error_t error;
 	zip_source_t *source = zip_source_filep_create(file, 0, -1, &error);
 	if (source == nullptr)
@@ -54,15 +51,16 @@ ArchiveFile* ZipArchive::OpenFile(const char* name)

 struct zip_file *zip_fopen_by_crc(struct zip *za, u32 crc, int flags)
 {
-    int i, n;
+    zip_uint64_t i;
+    zip_int64_t n;
    struct zip_stat stat;

    if (crc == 0) {
        return NULL;
    }

-    n = zip_get_num_files(za);
-    for (i = 0; i < n; i++) {
+    n = zip_get_num_entries(za, 0);
+    for (i = 0; i < (zip_uint64_t)n; i++) {
        if (zip_stat_index(za, i, flags, &stat) < -1) {
            return NULL;
        }
@@ -88,3 +86,23 @@ u32 ZipArchiveFile::Read(void* buffer, u32 length)
 {
 	return zip_fread(zip_file, buffer, length);
 }
+
+bool ZipArchive::Open(const void *data, size_t size)
+{
+	zip_error_t error;
+	zip_source_t *source = zip_source_buffer_create(data, size, 0, &error);
+	if (source == nullptr)
+		return false;
+	zip = zip_open_from_source(source, 0, NULL);
+	if (zip == nullptr)
+		zip_source_free(source);
+	return zip != nullptr;
+}
+
+ArchiveFile *ZipArchive::OpenFirstFile()
+{
+	zip_file *zipFile = zip_fopen_index(zip, 0, 0);
+	if (zipFile == nullptr)
+		return nullptr;
+	return new ZipArchiveFile(zipFile);
+}
@@ -32,9 +32,13 @@ public:
 	ArchiveFile* OpenFile(const char* name) override;
 	ArchiveFile* OpenFileByCrc(u32 crc) override;

-private:
-	bool Open(const char* path) override;
+	bool Open(const void *data, size_t size);
+	ArchiveFile *OpenFirstFile();

+protected:
+	bool Open(FILE *file) override;
+
+private:
 	struct zip *zip;
 };

@@ -22,24 +22,61 @@
 #include "archive.h"
 #include "7zArchive.h"
 #include "ZipArchive.h"
+#include "oslib/storage.h"

-Archive *OpenArchive(const char *path)
+Archive *OpenArchive(const std::string& path)
 {
-	std::string base_path(path);
-
-	Archive *sz_archive = new SzArchive();
-	if (sz_archive->Open(base_path.c_str()) || sz_archive->Open((base_path + ".7z").c_str()) || sz_archive->Open((base_path + ".7Z").c_str()))
-		return sz_archive;
-	delete sz_archive;
-
+	FILE *file = nullptr;
+	hostfs::FileInfo fileInfo;
+	try {
+		fileInfo = hostfs::storage().getFileInfo(path);
+		if (!fileInfo.isDirectory)
+			file = hostfs::storage().openFile(path, "rb");
+	} catch (const hostfs::StorageException& e) {
+	}
+	if (file == nullptr)
+	{
+		file = hostfs::storage().openFile(path + ".7z", "rb");
+		if (file == nullptr)
+			file = hostfs::storage().openFile(path + ".7Z", "rb");
+	}
+	if (file != nullptr)
+	{
+		Archive *sz_archive = new SzArchive();
+		if (sz_archive->Open(file))
+			return sz_archive;
+		delete sz_archive;
+		file = nullptr;
+	}
+	// Retry as a zip file
+	try {
+		if (!fileInfo.isDirectory)
+			file = hostfs::storage().openFile(path, "rb");
+	} catch (const hostfs::StorageException& e) {
+	}
+	if (file == nullptr)
+	{
+		file = hostfs::storage().openFile(path + ".zip", "rb");
+		if (file == nullptr)
+		{
+			file = hostfs::storage().openFile(path + ".ZIP", "rb");
+			if (file == nullptr)
+				return nullptr;
+		}
+	}
 	Archive *zip_archive = new ZipArchive();
-	if (zip_archive->Open(base_path.c_str()) || zip_archive->Open((base_path + ".zip").c_str()) || zip_archive->Open((base_path + ".ZIP").c_str()))
+	if (zip_archive->Open(file))
 		return zip_archive;
 	delete zip_archive;

-	return NULL;
+	return nullptr;
 }

-
-
+bool Archive::Open(const char* path)
+{
+	FILE *file = nowide::fopen(path, "rb");
+	if (file == nullptr)
+		return false;
+	return Open(file);
+}

@@ -36,10 +36,13 @@ public:
 	virtual ArchiveFile *OpenFile(const char *name) = 0;
 	virtual ArchiveFile *OpenFileByCrc(u32 crc) = 0;

-	friend Archive *OpenArchive(const char *path);
+protected:
+	virtual bool Open(FILE *file) = 0;

 private:
-	virtual bool Open(const char *name) = 0;
+	bool Open(const char *name);
+
+	friend Archive *OpenArchive(const std::string& path);
 };

-Archive *OpenArchive(const char *path);
+Archive *OpenArchive(const std::string& path);
@@ -19,11 +19,14 @@
 #include "rzip.h"
 #include <zlib.h>

+#include <cstring>
+
 const u8 RZipHeader[8] = { '#', 'R', 'Z', 'I', 'P', 'v', 1, '#' };

 bool RZipFile::Open(const std::string& path, bool write)
 {
 	verify(file == nullptr);
+	this->write = write;

 	file = nowide::fopen(path.c_str(), write ? "wb" : "rb");
 	if (file == nullptr)
@@ -49,6 +52,17 @@ bool RZipFile::Open(const std::string& path, bool write)
 		chunkIndex = 0;
 		chunkSize = 0;
 	}
+	else
+	{
+		maxChunkSize = 1_MB;
+		if (std::fwrite(RZipHeader, sizeof(RZipHeader), 1, file) != 1
+			|| std::fwrite(&maxChunkSize, sizeof(maxChunkSize), 1, file) != 1
+			|| std::fwrite(&size, sizeof(size), 1, file) != 1)
+		{
+			Close();
+			return false;
+		}
+	}

 	return true;
 }
@@ -57,6 +71,11 @@ void RZipFile::Close()
 {
 	if (file != nullptr)
 	{
+		if (write)
+		{
+			std::fseek(file, sizeof(RZipHeader) + sizeof(maxChunkSize), SEEK_SET);
+			std::fwrite(&size, sizeof(size), 1, file);
+		}
 		std::fclose(file);
 		file = nullptr;
 		if (chunk != nullptr)
@@ -70,6 +89,7 @@ void RZipFile::Close()
 size_t RZipFile::Read(void *data, size_t length)
 {
 	verify(file != nullptr);
+	verify(!write);

 	u8 *p = (u8 *)data;
 	size_t rv = 0;
@@ -99,7 +119,7 @@ size_t RZipFile::Read(void *data, size_t length)
 			delete [] zipped;
 			chunkSize = (u32)tl;
 		}
-		u32 l = std::min(chunkSize - chunkIndex, (u32)length);
+		u32 l = std::min(chunkSize - chunkIndex, (u32)(length - rv));
 		memcpy(p, chunk + chunkIndex, l);
 		p += l;
 		chunkIndex += l;
@@ -112,14 +132,9 @@ size_t RZipFile::Read(void *data, size_t length)
 size_t RZipFile::Write(const void *data, size_t length)
 {
 	verify(file != nullptr);
-	verify(std::ftell(file) == 0);
+	verify(write);

-	maxChunkSize = 1024 * 1024;
-	size = length;
-	if (std::fwrite(RZipHeader, sizeof(RZipHeader), 1, file) != 1
-		|| std::fwrite(&maxChunkSize, sizeof(maxChunkSize), 1, file) != 1
-		|| std::fwrite(&size, sizeof(size), 1, file) != 1)
-		return 0;
+	size += length;
 	const u8 *p = (const u8 *)data;
 	// compression output buffer must be 0.1% larger + 12 bytes
 	uLongf maxZippedSize = maxChunkSize + maxChunkSize / 1000 + 12;
@@ -32,6 +32,7 @@ public:
 	size_t Size() const { return size; }
 	size_t Read(void *data, size_t length);
 	size_t Write(const void *data, size_t length);
+	FILE *rawFile() const { return file; }

 private:
 	FILE *file = nullptr;
@@ -40,4 +41,5 @@ private:
 	u8 *chunk = nullptr;
 	u32 chunkSize = 0;
 	u32 chunkIndex = 0;
+	bool write = false;
 };
@@ -1,134 +1,16 @@
-/*
-	reicast build options
-
-		Reicast can support a lot of stuff, and this is an attempt
-		to organize the build time options
-
-		Option categories
-
-			BUILD_* - BUILD_COMPILER, etc...
-				definitions about the build machine
-
-			HOST_*	
-				definitions about the host machine
-
-			FEAT_*
-				definitions about the features that this build targets
-				This is higly related to HOST_*, but it's for options that might
-				or might not be avaiable depending on the target host, or that 
-				features that are irrelevant of	the host
-
-				Eg, Alsa, Pulse Audio and OSS might sense as HOST dedinitions
-				but it usually makes more sense to detect them as runtime. In
-				that context, HOST_ALSA makes no sense because the host might
-				or might not have alsa installed/ running
-
-				MMU makes no sense as a HOST definition at all, so it should
-				be FEAT_HAS_MMU
-
-			TARGET_*
-				A preconfigured default. Eg TARGET_WIN86. 
-
-		Naming of options, option values, and how to use them
-			
-			for options that makes sense to have a list of values
-				{CATEGORY}_{OPTION} 
-				{OPTION}_{VALUE}
-
-				eg.
-				BUILD_COMPILER == COMPILER_GCC, HOST_CPU != CPU_X64, ...
-
-			for options that are boolean
-				{CATEGORY}_IS_{OPTION} or {CATEGORY}_HAS_{OPTION} 
-				
-				Evaluates to 0 or 1
-
-			If an configuration cannot be neatly split into a set of
-			of orthogonal options, then it makes sense to break things
-			to "sets" or have a hierarchy of options. 
-
-			Example
-			-------
-			
-			In the beggining it made sense to have an audio backend
-			per operating system. It made sense to have it depend 
-			on HOST_OS and seleect DirectSound or alsa. 
-
-				// no option needed
-
-			Then, as android was introduced, which also uses OS_LINUX
-			atm, the audio could have been made an option. It could be
-			a HOST_* option, or FEAT_* one. I'd prefer FEAT_*. 
-			FEAT_* makes more sense as future wise we might want
-			to support multiple backends.
-				
-				FEAT_AUDIO_BACKEND
-					AUDIO_BACKEND_NONE
-					AUDIO_BACKEND_DS
-					AUDIO_BACKEND_ALSA
-					AUDIO_BACKEND_ANDROID
-
-				Used like
-					#if FEAT_AUDIO_BACKEND == AUDIO_BACKEND_DS ....
-			
-			At some point, we might have multiple audio backends that
-			can be compiled in and autodetected/selected at runtime.
-			In that case, it might make sense to have the options like
-
-					FEAT_HAS_ALSA
-					FEAT_HAS_DIRECTSOUND
-					FEAT_HAS_ANDROID_AUDIO
-
-				or 
-					FEAT_HAS_AUDIO_ALSA
-					FEAT_HAS_AUDIO_DS
-					FEAT_HAS_AUDIO_ANDROID
-
-				The none option might or might not make sense. In this
-				case it can be removed, as it should always be avaiable.
-
-			Guidelines
-			----------
-
-			General rule of thumb, don't overcomplicate things. Start
-			with a simple option, and then make it more complicated
-			as new uses apply (see the example above)
-
-			Don't use too long names, don't use too cryptic names. 
-			Most team developers should be able to understand or
-			figure out most of the acronyms used. 
-
-			Try to be consistent on the acronyms across all definitions
-
-			Code shouldn't depend on build level options whenever possible
-
-			Generally, the file should compile even if the option/module is
-			disabled. This makes makefiles etc much easier to write
-
-			TARGET_* options should generally only be used in this file
-
-			The current source is *not* good example of these guidelines
-
-		We'll try to be smart and figure out some options/defaults on this file
-		but this shouldn't get too complicated
-
-
-*/
-
+#pragma once
 //#define STRICT_MODE
 #ifndef STRICT_MODE
 #define FAST_MMU
 #define USE_WINCE_HACK
 #endif

-#define DC_PLATFORM_MASK        7
-#define DC_PLATFORM_DREAMCAST   0   /* Works, for the most part */
-#define DC_PLATFORM_DEV_UNIT    1   /* This is missing hardware */
-#define DC_PLATFORM_NAOMI       2   /* Works, for the most part */ 
-#define DC_PLATFORM_NAOMI2      3   /* Needs to be done, 2xsh4 + 2xpvr + custom TNL */
-#define DC_PLATFORM_ATOMISWAVE  4   /* Works, for the most part */
-#define DC_PLATFORM_HIKARU      5   /* Needs to be done, 2xsh4, 2x aica , custom vpu */
-#define DC_PLATFORM_AURORA      6   /* Needs to be done, Uses newer 300 mhz sh4 + 150 mhz pvr mbx SoC */
+#define DC_PLATFORM_DREAMCAST   0
+#define DC_PLATFORM_DEV_UNIT    1
+#define DC_PLATFORM_NAOMI       2
+#define DC_PLATFORM_NAOMI2      3
+#define DC_PLATFORM_ATOMISWAVE  4
+#define DC_PLATFORM_SYSTEMSP    5

 //HOST_CPU
 #define CPU_X86      0x20000001
@@ -139,13 +21,10 @@
 #define CPU_PPC      0x20000006
 #define CPU_PPC64    0x20000007
 #define CPU_ARM64    0x20000008
-#define CPU_MIPS64   0x20000009

 //FEAT_SHREC, FEAT_AREC, FEAT_DSPREC
 #define DYNAREC_NONE	0x40000001
 #define DYNAREC_JIT		0x40000002
-#define DYNAREC_CPP		0x40000003
-

 //automatic

@@ -175,12 +54,6 @@
 #define FEAT_DSPREC DYNAREC_NONE
 #endif

-#if defined(TARGET_NO_JIT)
-#define FEAT_SHREC DYNAREC_CPP
-#define FEAT_AREC DYNAREC_NONE
-#define FEAT_DSPREC DYNAREC_NONE
-#endif
-
 #ifdef __SWITCH__
 #define FEAT_NO_RWX_PAGES
 #endif
@@ -218,22 +91,30 @@
 #endif
 #endif

+#ifdef _WIN32
+#if defined(WINAPI_FAMILY) && (WINAPI_FAMILY == WINAPI_FAMILY_APP)
+#define TARGET_UWP
+#endif
+#ifdef HAVE_D3D11
+#define USE_DX11
+#endif
+#endif
+
+#if !defined(LIBRETRO) && !defined(TARGET_NO_EXCEPTIONS)
+#define USE_GGPO
+#endif
+
+#if !defined(__ANDROID__) && !defined(TARGET_IPHONE) && !defined(TARGET_UWP) \
+	&& !defined(__SWITCH__) && !defined(LIBRETRO) && !defined(__NetBSD__) && !defined(__OpenBSD__)
+#define NAOMI_MULTIBOARD
+#endif

 // TARGET PLATFORM
-
-#define RAM_SIZE_MAX (32*1024*1024)
-#define VRAM_SIZE_MAX (16*1024*1024)
-#define ARAM_SIZE_MAX (8*1024*1024)
-
-#define GD_CLOCK 33868800				//GDROM XTAL -- 768fs
-
-#define AICA_CORE_CLOCK (GD_CLOCK*4/3)		//[45158400]  GD->PLL 3:4 -> AICA CORE	 -- 1024fs
-#define ADAC_CLOCK (AICA_CORE_CLOCK/4)		//[11289600]  44100*256, AICA CORE -> PLL 4:1 -> ADAC -- 256fs
-#define AICA_ARM_CLOCK (AICA_CORE_CLOCK/2)	//[22579200]  AICA CORE -> PLL 2:1 -> ARM
-#define AICA_SDRAM_CLOCK (GD_CLOCK*2)		//[67737600]  GD-> PLL 2 -> SDRAM
-#define SH4_MAIN_CLOCK (200*1000*1000)		//[200000000] XTal(13.5) -> PLL (33.3) -> PLL 1:6 (200)
-#define SH4_RAM_CLOCK (100*1000*1000)		//[100000000] XTal(13.5) -> PLL (33.3) -> PLL 1:3 (100)	, also suplied to HOLLY chip
-#define G2_BUS_CLOCK (25*1000*1000)			//[25000000]  from Holly, from SH4_RAM_CLOCK w/ 2 2:1 plls
+#define GD_CLOCK 33868800						//GDROM XTAL -- 768fs
+#define AICA_CORE_CLOCK (GD_CLOCK * 4 / 3)		//[45158400]  GD->PLL 3:4 -> AICA CORE	 -- 1024fs
+#define AICA_ARM_CLOCK (AICA_CORE_CLOCK / 2)	//[22579200]  AICA CORE -> PLL 2:1 -> ARM
+#define SH4_MAIN_CLOCK (200 * 1000 * 1000)		//[200000000] XTal(13.5) -> PLL (33.3) -> PLL 1:6 (200)
+#define G2_BUS_CLOCK (25 * 1000 * 1000)			//[25000000]  from Holly, from SH4_RAM_CLOCK w/ 2 2:1 plls

 #if defined(GLES) && !defined(GLES3) && !defined(GLES2)
 // Only use GL ES 2.0 API functions
@@ -82,6 +82,13 @@ s32 cfgLoadInt(const std::string& section, const std::string& key, s32 def)
 	return cfgdb.get_int(section, key, def);
 }

+int64_t cfgLoadInt64(const std::string& section, const std::string& key, int64_t def) {
+	return cfgdb.get_int64(section, key, def);
+}
+void cfgSaveInt64(const std::string& section, const std::string& key, int64_t value) {
+	cfgdb.set_int64(section, key, value);
+}
+
 void  cfgSaveBool(const std::string& section, const std::string& key, bool value)
 {
 	cfgSaveStr(section, key, value ? "yes" : "no");
@@ -112,6 +119,11 @@ void cfgDeleteSection(const std::string& section)
 	cfgdb.delete_section(section);
 }

+void cfgDeleteEntry(const std::string& section, const std::string& key)
+{
+	cfgdb.delete_entry(section, key);
+}
+
 void cfgSetAutoSave(bool autoSave)
 {
 	::autoSave = autoSave;
@@ -5,6 +5,8 @@
 bool cfgOpen();
 s32 cfgLoadInt(const std::string& section, const std::string& key, s32 def);
 void cfgSaveInt(const std::string& section, const std::string& key, s32 value);
+int64_t cfgLoadInt64(const std::string& section, const std::string& key, int64_t def);
+void cfgSaveInt64(const std::string& section, const std::string& key, int64_t value);
 std::string cfgLoadStr(const std::string& section, const std::string& key, const std::string& def);
 void cfgSaveStr(const std::string& section, const std::string& key, const std::string& value);
 void cfgSaveBool(const std::string& section, const std::string& key, bool value);
@@ -12,8 +14,9 @@ bool cfgLoadBool(const std::string& section, const std::string& key, bool def);
 void cfgSetVirtual(const std::string& section, const std::string& key, const std::string& value);
 bool cfgIsVirtual(const std::string& section, const std::string& key);

-bool ParseCommandLine(int argc, char *argv[]);
+void ParseCommandLine(int argc, char *argv[]);

 void cfgSetAutoSave(bool autoSave);
 bool cfgHasSection(const std::string& section);
 void cfgDeleteSection(const std::string& section);
+void cfgDeleteEntry(const std::string& section, const std::string& key);
@@ -1,92 +1,66 @@
 /*
 	Command line parsing
-	~yay~
-
-	Nothing too interesting here, really
 */

 #include <cstdio>
-#include <cctype>
 #include <cstring>

 #include "cfg/cfg.h"
+#include "stdclass.h"

-char* trim_ws(char* str)
-{
-	if (str==0 || strlen(str)==0)
-		return 0;
-
-	while(*str)
-	{
-		if (!isspace(*str))
-			break;
-		str++;
-	}
-
-	size_t l=strlen(str);
-	
-	if (l==0)
-		return 0;
-
-	while(l>0)
-	{
-		if (!isspace(str[l-1]))
-			break;
-		str[l-1]=0;
-		l--;
-	}
-
-	if (l==0)
-		return 0;
-
-	return str;
-}
-
-int setconfig(char** arg,int cl)
+static int setconfig(char *arg[], int cl)
 {
 	int rv=0;
-	for(;;)
+
+	if (cl < 1)
 	{
-		if (cl<1)
+		WARN_LOG(COMMON, "-config : invalid number of parameters, format is section:key=value,section:key=value,...");
+		return rv;
+	}
+
+	std::string value(arg[1]);
+	for(;;)
+	{		
+		auto seppos = value.find(':');
+		if (seppos == std::string::npos)
 		{
-			WARN_LOG(COMMON, "-config : invalid number of parameters, format is section:key=value");
-			return rv;
+			WARN_LOG(COMMON, "-config : invalid parameter %s, format is section:key=value,section:key=value,...", value.c_str());
+			break;
 		}
-		char* sep=strstr(arg[1],":");
-		if (sep==0)
+		auto eqpos = value.find('=', seppos);
+		if (eqpos == std::string::npos)
 		{
-			WARN_LOG(COMMON, "-config : invalid parameter %s, format is section:key=value", arg[1]);
-			return rv;
-		}
-		char* value=strstr(sep+1,"=");
-		if (value==0)
-		{
-			WARN_LOG(COMMON, "-config : invalid parameter %s, format is section:key=value", arg[1]);
-			return rv;
+			WARN_LOG(COMMON, "-config : invalid parameter %s, format is section:key=value,section:key=value,...", value.c_str());
+			break;
 		}

-		*sep++=0;
-		*value++=0;
+		auto commapos = value.find(',', eqpos);

-		char* sect=trim_ws(arg[1]);
-		char* key=trim_ws(sep);
-		value=trim_ws(value);
+		std::string sect = trim_ws(value.substr(0, seppos));
+		std::string key = trim_ws(value.substr(seppos + 1, eqpos - seppos - 1));
+		auto endofcurrent = (commapos == std::string::npos) ? value.size() : commapos;
+		std::string next = (commapos == std::string::npos) ? "" : trim_ws(value.substr(endofcurrent + 1, value.size() - endofcurrent));
+		value = trim_ws(value.substr(eqpos + 1, endofcurrent - eqpos - 1));

-		if (sect==0 || key==0)
+		if (sect.empty() || key.empty())
 		{
-			WARN_LOG(COMMON, "-config : invalid parameter, format is section:key=value");
-			return rv;
+			WARN_LOG(COMMON, "-config : invalid parameter, format is section:key=value,section:key=value,...");
+			break;
 		}

-		const char* constval = value;
-		if (constval==0)
-			constval="";
-		INFO_LOG(COMMON, "Virtual cfg %s:%s=%s", sect, key, constval);
+		INFO_LOG(COMMON, "Virtual cfg %s:%s=%s", sect.c_str(), key.c_str(), value.c_str());

-		cfgSetVirtual(sect, key, constval);
-		rv++;
+		cfgSetVirtual(sect, key, value);

-		if (cl>=3 && stricmp(arg[2],",")==0)
+		if (commapos == std::string::npos)
+			rv++;
+
+		if (commapos != std::string::npos)
+		{
+			value = next;
+			continue;
+		}
+		else if (cl>=3 && strcmp(arg[2],",")==0)
 		{
 			cl-=2;
 			arg+=2;
@@ -112,9 +86,9 @@ static int showhelp()
 	return 0;
 }

-bool ParseCommandLine(int argc,char* argv[])
+void ParseCommandLine(int argc,char* argv[])
 {
-	settings.imgread.ImagePath[0] = '\0';
+	settings.content.path.clear();
 	int cl=argc-2;
 	char** arg=argv+1;
 	while(cl>=0)
@@ -136,6 +110,10 @@ bool ParseCommandLine(int argc,char* argv[])
 			cl--;
 		}
 #endif
+		else if ((*arg)[0] == '-')
+		{
+			WARN_LOG(COMMON, "Ignoring unknown command line option '%s'", *arg);
+		}
 		else
 		{
 			char* extension = strrchr(*arg, '.');
@@ -145,22 +123,21 @@ bool ParseCommandLine(int argc,char* argv[])
 					|| stricmp(extension, ".gdi") == 0 || stricmp(extension, ".cue") == 0))
 			{
 				INFO_LOG(COMMON, "Using '%s' as cd image", *arg);
-				strcpy(settings.imgread.ImagePath, *arg);
+				settings.content.path = *arg;
 			}
 			else if (extension && stricmp(extension, ".elf") == 0)
 			{
 				INFO_LOG(COMMON, "Using '%s' as reios elf file", *arg);
 				cfgSetVirtual("config", "bios.UseReios", "yes");
-				strcpy(settings.imgread.ImagePath, *arg);
+				settings.content.path = *arg;
 			}
 			else
 			{
 				INFO_LOG(COMMON, "Using '%s' as rom", *arg);
-				strcpy(settings.imgread.ImagePath, *arg);
+				settings.content.path = *arg;
 			}
 		}
 		arg++;
 		cl--;
 	}
-	return false;
 }
@@ -1,8 +1,7 @@
 #include "ini.h"
 #include "types.h"
 #include <sstream>
-
-char* trim_ws(char* str);
+#include "stdclass.h"

 namespace emucfg {

@@ -25,6 +24,14 @@ int ConfigEntry::get_int()
 	}
 }

+int64_t ConfigEntry::get_int64()
+{
+	int base = 10;
+	if (strstr(this->value.c_str(), "0x") != nullptr)
+		base = 16;
+	return (int64_t)strtoll(this->value.c_str(), nullptr, base);
+}
+
 bool ConfigEntry::get_bool()
 {
 	if (stricmp(this->value.c_str(), "yes") == 0 ||
@@ -159,6 +166,19 @@ int ConfigFile::get_int(const std::string& section_name, const std::string& entr
 	}
 }

+int64_t ConfigFile::get_int64(const std::string& section_name, const std::string& entry_name, int64_t default_value)
+{
+	ConfigEntry* entry = this->get_entry(section_name, entry_name);
+	if (entry == NULL)
+	{
+		return default_value;
+	}
+	else
+	{
+		return entry->get_int64();
+	}
+}
+
 bool ConfigFile::get_bool(const std::string& section_name, const std::string& entry_name, bool default_value)
 {
 	ConfigEntry* entry = this->get_entry(section_name, entry_name);
@@ -189,6 +209,13 @@ void ConfigFile::set_int(const std::string& section_name, const std::string& ent
 	this->set(section_name, entry_name, str_value.str(), is_virtual);
 }

+void ConfigFile::set_int64(const std::string& section_name, const std::string& entry_name, int64_t value, bool is_virtual)
+{
+	std::stringstream str_value;
+	str_value << value;
+	this->set(section_name, entry_name, str_value.str(), is_virtual);
+}
+
 void ConfigFile::set_bool(const std::string& section_name, const std::string& entry_name, bool value, bool is_virtual)
 {
 	std::string str_value = (value ? "yes" : "no");
@@ -197,94 +224,53 @@ void ConfigFile::set_bool(const std::string& section_name, const std::string& en

 void ConfigFile::parse(FILE* file)
 {
-	if(file == NULL)
-	{
+	if (file == nullptr)
 		return;
-	}
+
 	char line[512];
-	char current_section[512] = { '\0' };
+	std::string section;
 	int cline = 0;
-	while(file && !feof(file))
+	while (true)
 	{
-		if (std::fgets(line, 512, file) == NULL || std::feof(file))
-		{
+		if (std::fgets(line, sizeof(line), file) == nullptr)
 			break;
-		}
-
 		cline++;
-
-		if (strlen(line) < 3)
+		std::string s(line);
+		s = trim_ws(s, " \r\n");
+		if (s.empty())
+			continue;
+		if (s.length() >= 3 && s[0] == '[' && s[s.length() - 1] == ']')
 		{
+			section = s.substr(1, s.length() - 2);
 			continue;
 		}
-
-		if (line[strlen(line)-1] == '\r' ||
-			  line[strlen(line)-1] == '\n')
+		auto eqpos = s.find('=');
+		if (eqpos == std::string::npos)
 		{
-			line[strlen(line)-1] = '\0';
-		}
-
-		char* tl = trim_ws(line);
-
-		if (tl[0] == '[' && tl[strlen(tl)-1] == ']')
-		{
-			tl[strlen(tl)-1] = '\0';
-
-			// FIXME: Data loss if buffer is too small
-			strncpy(current_section, tl+1, sizeof(current_section));
-			current_section[sizeof(current_section) - 1] = '\0';
-
-			trim_ws(current_section);
-		}
-		else
-		{
-			if (strlen(current_section) == 0)
-			{
-				continue; //no open section
-			}
-
-			char* separator = strstr(tl, "=");
-
-			if (!separator)
-			{
-				WARN_LOG(COMMON, "Malformed entry on config - ignoring @ %d(%s)", cline, tl);
-				continue;
-			}
-
-			*separator = '\0';
-
-			char* name = trim_ws(tl);
-			char* value = trim_ws(separator + 1);
-			if (name == NULL || value == NULL)
-			{
-				//printf("Malformed entry on config - ignoring @ %d(%s)\n",cline, tl);
-				continue;
-			}
-			else
-			{
-				this->set(std::string(current_section), std::string(name), std::string(value));
-			}
+			WARN_LOG(COMMON, "Malformed entry on config - ignoring line %d: %s", cline, s.c_str());
+			continue;
 		}
+		std::string property = trim_ws(s.substr(0, eqpos));
+		std::string value = trim_ws(s.substr(eqpos + 1));
+		if (value.length() >= 2 && value[0] == '"' && value[value.length() - 1] == '"')
+			value = value.substr(1, value.length() - 2);
+		set(section, property, value);
 	}
 }

 void ConfigFile::save(FILE* file)
 {
-	for (const auto& section_it : this->sections)
+	for (const auto& [section_name, section] : this->sections)
 	{
-		const std::string& section_name = section_it.first;
-		const ConfigSection& section = section_it.second;
+		if (!section_name.empty())
+			std::fprintf(file, "[%s]\n", section_name.c_str());

-		std::fprintf(file, "[%s]\n", section_name.c_str());
-
-		for (const auto& entry_it : section.entries)
+		for (const auto& [entry_name, entry] : section.entries)
 		{
-			const std::string& entry_name = entry_it.first;
-			const ConfigEntry& entry = entry_it.second;
 			std::fprintf(file, "%s = %s\n", entry_name.c_str(), entry.get_string().c_str());
 		}
-
-		std::fputs("\n", file);
+		if (!section_name.empty())
+			std::fputc('\n', file);
 	}
 }

@@ -3,6 +3,7 @@
 #include <cstdio>
 #include <map>
 #include <string>
+#include <cstdint>

 namespace emucfg {

@@ -11,6 +12,7 @@ struct ConfigEntry {
 	const std::string& get_string() const;
 	int get_int();
 	bool get_bool();
+	int64_t get_int64();
 };

 struct ConfigSection {
@@ -41,10 +43,12 @@ struct ConfigFile {
 		/* getting values */
 		std::string get(const std::string& section_name, const std::string& entry_name, const std::string& default_value = "");
 		int get_int(const std::string& section_name, const std::string& entry_name, int default_value = 0);
+		int64_t get_int64(const std::string& section_name, const std::string& entry_name, int64_t default_value = 0);
 		bool get_bool(const std::string& section_name, const std::string& entry_name, bool default_value = false);
 		/* setting values */
 		void set(const std::string& section_name, const std::string& entry_name, const std::string& value, bool is_virtual = false);
 		void set_int(const std::string& section_name, const std::string& entry_name, int value, bool is_virtual = false);
+		void set_int64(const std::string& section_name, const std::string& entry_name, int64_t value, bool is_virtual = false);
 		void set_bool(const std::string& section_name, const std::string& entry_name, bool value, bool is_virtual = false);

 		void delete_section(const std::string& section_name);
@@ -17,14 +17,15 @@
    along with Flycast.  If not, see <https://www.gnu.org/licenses/>.
 */
 #include "option.h"
+#include "network/naomi_network.h"
+#include "debug/gdb_server.h"

 namespace config {

 // Dynarec

 Option<bool> DynarecEnabled("Dynarec.Enabled", true);
-Option<bool> DynarecIdleSkip("Dynarec.idleskip", true);
-Option<bool> DynarecSafeMode("Dynarec.safe-mode");
+Option<int> Sh4Clock("Sh4Clock", 200);

 // General

@@ -32,16 +33,17 @@ Option<int> Cable("Dreamcast.Cable", 3);			// TV Composite
 Option<int> Region("Dreamcast.Region", 1);			// USA
 Option<int> Broadcast("Dreamcast.Broadcast", 0);	// NTSC
 Option<int> Language("Dreamcast.Language", 1);		// English
-Option<bool> FullMMU("Dreamcast.FullMMU");
 Option<bool> ForceWindowsCE("Dreamcast.ForceWindowsCE");
 Option<bool> AutoLoadState("Dreamcast.AutoLoadState");
 Option<bool> AutoSaveState("Dreamcast.AutoSaveState");
-Option<int> SavestateSlot("Dreamcast.SavestateSlot");
+Option<int, false> SavestateSlot("Dreamcast.SavestateSlot");
+Option<bool> ForceFreePlay("ForceFreePlay", true);
+Option<bool, false> FetchBoxart("FetchBoxart", true);
+Option<bool, false> BoxartDisplayMode("BoxartDisplayMode", true);

 // Sound

 Option<bool> DSPEnabled("aica.DSPEnabled", false);
-Option<bool> DisableSound("aica.NoSound");
 #if HOST_CPU == CPU_ARM
 Option<int> AudioBufferSize("aica.BufferSize", 5644);	// 128 ms
 #else
@@ -57,6 +59,7 @@ Option<bool> AutoLatency("aica.AutoLatency",

 OptionString AudioBackend("backend", "auto", "audio");
 AudioVolumeOption AudioVolume;
+Option<bool> VmuSound("VmuSound", false, "audio");

 // Rendering

@@ -95,21 +98,42 @@ Option<int> MaxThreads("pvr.MaxThreads", 3);
 Option<int> AutoSkipFrame("pvr.AutoSkipFrame", 0);
 Option<int> RenderResolution("rend.Resolution", 480);
 Option<bool> VSync("rend.vsync", true);
-Option<u64> PixelBufferSize("rend.PixelBufferSize", 512 * 1024 * 1024);
+Option<int64_t> PixelBufferSize("rend.PixelBufferSize", 512_MB);
 Option<int> AnisotropicFiltering("rend.AnisotropicFiltering", 1);
+Option<int> TextureFiltering("rend.TextureFiltering", 0); // Default
 Option<bool> ThreadedRendering("rend.ThreadedRendering", true);
+Option<bool> DupeFrames("rend.DupeFrames", false);
+Option<int> PerPixelLayers("rend.PerPixelLayers", 32);
+Option<bool> NativeDepthInterpolation("rend.NativeDepthInterpolation", false);
+Option<bool> EmulateFramebuffer("rend.EmulateFramebuffer", false);
+#ifdef VIDEO_ROUTING
+Option<bool> VideoRouting("rend.VideoRouting", false);
+Option<bool> VideoRoutingScale("rend.VideoRoutingScale", false);
+Option<int> VideoRoutingVRes("rend.VideoRoutingVRes", 720);
+#endif

 // Misc

 Option<bool> SerialConsole("Debug.SerialConsoleEnabled");
 Option<bool> SerialPTY("Debug.SerialPTY");
+Option<bool> GDB("Debug.GDBEnabled");
+Option<int> GDBPort("Debug.GDBPort", debugger::DEFAULT_PORT);
+Option<bool> GDBWaitForConnection("Debug.GDBWaitForConnection");
 Option<bool> UseReios("UseReios");
 Option<bool> FastGDRomLoad("FastGDRomLoad", false);
+Option<bool> RamMod32MB("Dreamcast.RamMod32MB", false);

 Option<bool> OpenGlChecks("OpenGlChecks", false, "validate");

 Option<std::vector<std::string>, false> ContentPath("Dreamcast.ContentPath");
 Option<bool, false> HideLegacyNaomiRoms("Dreamcast.HideLegacyNaomiRoms", true);
+Option<bool, false> UploadCrashLogs("UploadCrashLogs", true);
+
+// Profiler
+Option<bool> ProfilerEnabled("Profiler.Enabled");
+Option<bool> ProfilerDrawToGUI("Profiler.DrawGUI");
+Option<bool> ProfilerOutputTTY("Profiler.OutputTTY");
+Option<float> ProfilerFrameWarningTime("Profiler.FrameWarningTime", 1.0f / 55.0f);

 // Network

@@ -117,7 +141,18 @@ Option<bool> NetworkEnable("Enable", false, "network");
 Option<bool> ActAsServer("ActAsServer", false, "network");
 OptionString DNS("DNS", "46.101.91.123", "network");
 OptionString NetworkServer("server", "", "network");
+Option<int> LocalPort("LocalPort", NaomiNetwork::SERVER_PORT, "network");
 Option<bool> EmulateBBA("EmulateBBA", false, "network");
+Option<bool> EnableUPnP("EnableUPnP", true, "network");
+Option<bool> GGPOEnable("GGPO", false, "network");
+Option<int> GGPODelay("GGPODelay", 0, "network");
+Option<bool> NetworkStats("Stats", true, "network");
+Option<int> GGPOAnalogAxes("GGPOAnalogAxes", 0, "network");
+Option<bool> GGPOChat("GGPOChat", true, "network");
+Option<bool> GGPOChatTimeoutToggle("GGPOChatTimeoutToggle", true, "network");
+Option<int> GGPOChatTimeout("GGPOChatTimeout", 10, "network");
+Option<bool> NetworkOutput("NetworkOutput", false, "network");
+Option<int> MultiboardSlaves("MultiboardSlaves", 1, "network");

 #ifdef SUPPORT_DISPMANX
 Option<bool> DispmanxMaintainAspect("maintain_aspect", true, "dispmanx");
@@ -152,8 +187,13 @@ std::array<std::array<Option<MapleDeviceType>, 2>, 4> MapleExpansionDevices {
 	Option<MapleDeviceType>("device4.1", MDT_None, "input"),
 	Option<MapleDeviceType>("device4.2", MDT_None, "input"),
 };
+Option<bool> PerGameVmu("PerGameVmu", false, "config");
 #ifdef _WIN32
-Option<bool> UseRawInput("RawInput", false, "input");
+Option<bool, false> UseRawInput("RawInput", false, "input");
+#endif
+
+#ifdef USE_LUA
+Option<std::string, false> LuaFileName("LuaFileName", "flycast.lua");
 #endif

 } // namespace config
@@ -21,6 +21,7 @@
 #include <vector>
 #include <array>
 #include <cmath>
+#include <type_traits>
 #include "cfg.h"
 #include "hw/maple/maple_cfg.h"
 #ifdef LIBRETRO
@@ -70,10 +71,6 @@ public:
 		cfgSetAutoSave(true);
 	}

-	const std::string& getGameId() const {
-		return gameId;
-	}
-
 	void setGameId(const std::string& gameId) {
 		this->gameId = gameId;
 	}
@@ -104,10 +101,6 @@ private:
 	friend class Option;
 };

-// Missing in C++11
-template <bool B, typename T = void>
-using enable_if_t = typename std::enable_if<B, T>::type;
-
 template<typename T, bool PerGameOption = true>
 class Option : public BaseOption {
 public:
@@ -125,7 +118,7 @@ public:

 	void load() override {
 		if (PerGameOption && settings.hasPerGameConfig())
-			set(doLoad(settings.getGameId(), section + "." + name));
+			set(doLoad(settings.gameId, section + "." + name));
 		else
 		{
 			set(doLoad(section, name));
@@ -146,10 +139,14 @@ public:
 		else if (PerGameOption && settings.hasPerGameConfig())
 		{
 			if (value == doLoad(section, name))
+			{
+				// delete existing per-game option if any
+				cfgDeleteEntry(settings.gameId, section + "." + name);
 				return;
+			}
 		}
 		if (PerGameOption && settings.hasPerGameConfig())
-			doSave(settings.getGameId(), section + "." + name);
+			doSave(settings.gameId, section + "." + name);
 		else
 			doSave(section, name);
 	}
@@ -157,8 +154,8 @@ public:
 	T& get() { return value; }
 	void set(T v) { value = v; }

-	void override(T v) {
-		verify(PerGameOption);
+	void override(T v)
+	{
 		overriddenDefault = v;
 		overridden = true;
 		value = v;
@@ -173,40 +170,47 @@ public:

 protected:
 	template <typename U = T>
-	enable_if_t<std::is_same<U, bool>::value, T>
+	std::enable_if_t<std::is_same_v<U, bool>, T>
 	doLoad(const std::string& section, const std::string& name) const
 	{
 		return cfgLoadBool(section, name, value);
 	}

 	template <typename U = T>
-	enable_if_t<(std::is_integral<U>::value || std::is_enum<U>::value)
-			&& !std::is_same<U, bool>::value, T>
+	std::enable_if_t<std::is_same<U, int64_t>::value, T>
+	doLoad(const std::string& section, const std::string& name) const
+	{
+		return cfgLoadInt64(section, name, value);
+	}
+
+	template <typename U = T>
+	std::enable_if_t<(std::is_integral_v<U> || std::is_enum_v<U>)
+			&& !std::is_same_v<U, bool> && !std::is_same_v<U, int64_t>, T>
 	doLoad(const std::string& section, const std::string& name) const
 	{
 		return (T)cfgLoadInt(section, name, (int)value);
 	}

 	template <typename U = T>
-	enable_if_t<std::is_same<U, std::string>::value, T>
+	std::enable_if_t<std::is_same_v<U, std::string>, T>
 	doLoad(const std::string& section, const std::string& name) const
 	{
 		return cfgLoadStr(section, name, value);
 	}

 	template <typename U = T>
-	enable_if_t<std::is_same<float, U>::value, T>
+	std::enable_if_t<std::is_same_v<float, U>, T>
 	doLoad(const std::string& section, const std::string& name) const
 	{
 		std::string strValue = cfgLoadStr(section, name, "");
 		if (strValue.empty())
 			return value;
 		else
-			return atof(strValue.c_str());
+			return (float)atof(strValue.c_str());
 	}

 	template <typename U = T>
-	enable_if_t<std::is_same<std::vector<std::string>, U>::value, T>
+	std::enable_if_t<std::is_same_v<std::vector<std::string>, U>, T>
 	doLoad(const std::string& section, const std::string& name) const
 	{
 		std::string paths = cfgLoadStr(section, name, "");
@@ -265,29 +269,36 @@ protected:
 	}

 	template <typename U = T>
-	enable_if_t<std::is_same<U, bool>::value>
+	std::enable_if_t<std::is_same_v<U, bool>>
 	doSave(const std::string& section, const std::string& name) const
 	{
 		cfgSaveBool(section, name, value);
 	}

 	template <typename U = T>
-	enable_if_t<(std::is_integral<U>::value || std::is_enum<U>::value)
-		&& !std::is_same<U, bool>::value>
+	std::enable_if_t<std::is_same<U, int64_t>::value>
+	doSave(const std::string& section, const std::string& name) const
+	{
+		cfgSaveInt64(section, name, value);
+	}
+
+	template <typename U = T>
+	std::enable_if_t<(std::is_integral_v<U> || std::is_enum_v<U>)
+		&& !std::is_same_v<U, bool> && !std::is_same_v<U, int64_t>>
 	doSave(const std::string& section, const std::string& name) const
 	{
 		cfgSaveInt(section, name, (int)value);
 	}

 	template <typename U = T>
-	enable_if_t<std::is_same<U, std::string>::value>
+	std::enable_if_t<std::is_same_v<U, std::string>>
 	doSave(const std::string& section, const std::string& name) const
 	{
 		cfgSaveStr(section, name, value);
 	}

 	template <typename U = T>
-	enable_if_t<std::is_same<float, U>::value>
+	std::enable_if_t<std::is_same_v<float, U>>
 	doSave(const std::string& section, const std::string& name) const
 	{
 		char buf[64];
@@ -296,7 +307,7 @@ protected:
 	}

 	template <typename U = T>
-	enable_if_t<std::is_same<std::vector<std::string>, U>::value>
+	std::enable_if_t<std::is_same_v<std::vector<std::string>, U>>
 	doSave(const std::string& section, const std::string& name) const
 	{
 		std::string s;
@@ -345,8 +356,9 @@ using OptionString = Option<std::string>;
 // Dynarec

 extern Option<bool> DynarecEnabled;
-extern Option<bool> DynarecIdleSkip;
-extern Option<bool> DynarecSafeMode;
+#ifndef LIBRETRO
+extern Option<int> Sh4Clock;
+#endif

 // General

@@ -354,17 +366,18 @@ extern Option<int> Cable;		// 0 -> VGA, 1 -> VGA, 2 -> RGB, 3 -> TV Composite
 extern Option<int> Region;		// 0 -> JP, 1 -> USA, 2 -> EU, 3 -> default
 extern Option<int> Broadcast;	// 0 -> NTSC, 1 -> PAL, 2 -> PAL/M, 3 -> PAL/N, 4 -> default
 extern Option<int> Language;	// 0 -> JP, 1 -> EN, 2 -> DE, 3 -> FR, 4 -> SP, 5 -> IT, 6 -> default
-extern Option<bool> FullMMU;
 extern Option<bool> ForceWindowsCE;
 extern Option<bool> AutoLoadState;
 extern Option<bool> AutoSaveState;
-extern Option<int> SavestateSlot;
+extern Option<int, false> SavestateSlot;
+extern Option<bool> ForceFreePlay;
+extern Option<bool, false> FetchBoxart;
+extern Option<bool, false> BoxartDisplayMode;

 // Sound

 constexpr bool LimitFPS = true;
 extern Option<bool> DSPEnabled;
-extern Option<bool> DisableSound;
 extern Option<int> AudioBufferSize;	//In samples ,*4 for bytes
 extern Option<bool> AutoLatency;

@@ -387,61 +400,36 @@ public:
 	void calcDbPower()
 	{
 		// dB scaling calculation: https://www.dr-lex.be/info-stuff/volumecontrols.html
-		logarithmic_volume_scale = fmin(exp(4.605 * float(value) / 100.0) / 100.0, 1.0);
+		logarithmic_volume_scale = std::min(std::exp(4.605f * float(value) / 100.f) / 100.f, 1.f);
 		if (value < 10)
-			logarithmic_volume_scale *= value / 10.0;
+			logarithmic_volume_scale *= value / 10.f;
 	}
 };
 extern AudioVolumeOption AudioVolume;
+extern Option<bool> VmuSound;

 // Rendering

 class RendererOption : public Option<RenderType> {
 public:
-	RendererOption()
-#ifdef _WIN32
-		: Option<RenderType>("pvr.rend", RenderType::DirectX9) {}
+	RendererOption() : Option<RenderType>("pvr.rend",
+#if defined(USE_DX11)
+			RenderType::DirectX11
+#elif defined(USE_DX9)
+			RenderType::DirectX9
+#elif !defined(USE_OPENGL)
+			RenderType::Vulkan
 #else
-		: Option<RenderType>("pvr.rend", RenderType::OpenGL) {}
+			RenderType::OpenGL
 #endif
+		) {}

-	bool isOpenGL() const {
-		return value == RenderType::OpenGL || value == RenderType::OpenGL_OIT;
-	}
-	bool isVulkan() const {
-		return value == RenderType::Vulkan || value == RenderType::Vulkan_OIT;
-	}
-	bool isDirectX() const {
-		return value == RenderType::DirectX9;
-	}
-
-	void set(RenderType v)
-	{
-		newValue = v;
-	}
 	RenderType& operator=(const RenderType& v) { set(v); return value; }

-	void load() override {
-		RenderType current = value;
-		Option<RenderType>::load();
-		newValue = value;
-		value = current;
-	}
-
 	void reset() override {
-		// don't reset the value to avoid vk -> gl -> vk quick switching
+		// don't reset the value to avoid quick switching when starting a game
 		overridden = false;
 	}
-
-	bool pendingChange() {
-		return newValue != value;
-	}
-	void commit() {
-		value = newValue;
-	}
-
-private:
-	RenderType newValue = RenderType();
 };
 extern RendererOption RendererType;
 extern Option<bool> UseMipmaps;
@@ -452,8 +440,11 @@ extern Option<bool> RenderToTextureBuffer;
 extern Option<bool> TranslucentPolygonDepthMask;
 extern Option<bool> ModifierVolumes;
 constexpr bool Clipping = true;
+#ifndef LIBRETRO
 extern Option<int> TextureUpscale;
 extern Option<int> MaxFilteredTextureSize;
+extern Option<int> PerPixelLayers;
+#endif
 extern Option<float> ExtraDepthScale;
 extern Option<bool> CustomTextures;
 extern Option<bool> DumpTextures;
@@ -470,21 +461,41 @@ extern Option<int> MaxThreads;
 extern Option<int> AutoSkipFrame;		// 0: none, 1: some, 2: more
 extern Option<int> RenderResolution;
 extern Option<bool> VSync;
-extern Option<u64> PixelBufferSize;
+extern Option<int64_t> PixelBufferSize;
 extern Option<int> AnisotropicFiltering;
+extern Option<int> TextureFiltering; // 0: default, 1: force nearest, 2: force linear
 extern Option<bool> ThreadedRendering;
+extern Option<bool> DupeFrames;
+extern Option<bool> NativeDepthInterpolation;
+extern Option<bool> EmulateFramebuffer;
+#ifdef VIDEO_ROUTING
+extern Option<bool> VideoRouting;
+extern Option<bool> VideoRoutingScale;
+extern Option<int> VideoRoutingVRes;
+#endif

 // Misc

 extern Option<bool> SerialConsole;
 extern Option<bool> SerialPTY;
+extern Option<bool> GDB;
+extern Option<int> GDBPort;
+extern Option<bool> GDBWaitForConnection;
 extern Option<bool> UseReios;
 extern Option<bool> FastGDRomLoad;
+extern Option<bool> RamMod32MB;

 extern Option<bool> OpenGlChecks;

 extern Option<std::vector<std::string>, false> ContentPath;
 extern Option<bool, false> HideLegacyNaomiRoms;
+extern Option<bool, false> UploadCrashLogs;
+
+// Profiling
+extern Option<bool> ProfilerEnabled;
+extern Option<bool> ProfilerDrawToGUI;
+extern Option<bool> ProfilerOutputTTY;
+extern Option<float> ProfilerFrameWarningTime;

 // Network

@@ -492,7 +503,18 @@ extern Option<bool> NetworkEnable;
 extern Option<bool> ActAsServer;
 extern OptionString DNS;
 extern OptionString NetworkServer;
+extern Option<int> LocalPort;
 extern Option<bool> EmulateBBA;
+extern Option<bool> EnableUPnP;
+extern Option<bool> GGPOEnable;
+extern Option<int> GGPODelay;
+extern Option<bool> NetworkStats;
+extern Option<int> GGPOAnalogAxes;
+extern Option<bool> GGPOChat;
+extern Option<bool> GGPOChatTimeoutToggle;
+extern Option<int> GGPOChatTimeout;
+extern Option<bool> NetworkOutput;
+extern Option<int> MultiboardSlaves;

 #ifdef SUPPORT_DISPMANX
 extern Option<bool> DispmanxMaintainAspect;
@@ -509,11 +531,15 @@ extern Option<int> MouseSensitivity;
 extern Option<int> VirtualGamepadVibration;
 extern std::array<Option<MapleDeviceType>, 4> MapleMainDevices;
 extern std::array<std::array<Option<MapleDeviceType>, 2>, 4> MapleExpansionDevices;
+extern Option<bool> PerGameVmu;
 #ifdef _WIN32
-extern Option<bool> UseRawInput;
+extern Option<bool, false> UseRawInput;
 #else
 constexpr bool UseRawInput = false;
 #endif

-} // namespace config
+#ifdef USE_LUA
+extern Option<std::string, false> LuaFileName;
+#endif

+} // namespace config
@@ -21,12 +21,15 @@
 #pragma once
 #include "types.h"

+#include <vector>
+
 struct WidescreenCheat
 {
 	const char *game_id;
 	const char *area_or_version;
 	u32 addresses[16];
 	u32 values[16];
+	u32 origValues[16];
 };

 struct Cheat
@@ -39,17 +42,30 @@ struct Cheat
 		runNextIfEq,
 		runNextIfNeq,
 		runNextIfGt,
-		runNextIfLt
+		runNextIfLt,
+		copy
 	};
-	Type type = Type::disabled;
+	Type type;
 	std::string description;
-	bool enabled = false;
-	u32 size = 0;
-	u32 address = 0;
-	u32 value = 0;
-	u32 repeatCount = 1;
-	u32 repeatValueIncrement = 0;
-	u32 repeatAddressIncrement = 0;
+	bool enabled;
+	u32 size;
+	u32 address;
+	u32 value;
+	u8 valueMask;
+	u32 repeatCount;
+	u32 repeatValueIncrement;
+	u32 repeatAddressIncrement;
+	u32 destAddress;
+	bool builtIn;
+
+	Cheat(Type type = Type::disabled, const std::string& description = "", bool enabled = false, u32 size = 0, u32 address = 0,
+			u32 value = 0, u8 valueMask = 0, u32 repeatCount = 1, u32 repeatValueIncrement = 0,
+			u32 repeatAddressIncrement = 0, u32 destAddress = 0, bool builtIn = false)
+		: type(type), description(description), enabled(enabled), size(size), address(address), value(value), valueMask(valueMask),
+		  repeatCount(repeatCount), repeatValueIncrement(repeatValueIncrement), repeatAddressIncrement(repeatAddressIncrement),
+		  destAddress(destAddress), builtIn(builtIn)
+	{
+	}
 };

 class CheatManager
@@ -62,12 +78,15 @@ public:
 	bool cheatEnabled(size_t index) const { return cheats[index].enabled; }
 	void enableCheat(size_t index, bool enabled) { cheats[index].enabled = enabled; }
 	void loadCheatFile(const std::string& filename);
+	void saveCheatFile(const std::string& filename);
 	// Returns true if using 16:9 anamorphic screen ratio
 	bool isWidescreen() const { return widescreen_cheat != nullptr; }
+	void addGameSharkCheat(const std::string& name, const std::string& s);

 private:
 	u32 readRam(u32 addr, u32 bits);
 	void writeRam(u32 addr, u32 value, u32 bits);
+	void setActive(bool active);

 	static const WidescreenCheat widescreen_cheats[];
 	static const WidescreenCheat naomi_widescreen_cheats[];
@@ -75,6 +94,10 @@ private:
 	bool active = false;
 	std::vector<Cheat> cheats;
 	std::string gameId;
+
+	friend class CheatManagerTest_TestLoad_Test;
+	friend class CheatManagerTest_TestGameShark_Test;
+	friend class CheatManagerTest_TestSave_Test;
 };

 extern CheatManager cheatManager;
@@ -73,20 +73,47 @@ const std::array<Sh4RegType, 59> Sh4RegList {
 class DebugAgent
 {
 public:
+	struct Breakpoint {
+		enum Type
+		{
+			BP_TYPE_SOFTWARE_BREAK,
+			BP_TYPE_HARDWARE_BREAK,
+			BP_TYPE_WRITE_WATCHPOINT,
+			BP_TYPE_READ_WATCHPOINT,
+			BP_TYPE_ACCESS_WATCHPOINT,
+			BP_TYPE_COUNT
+		};
+
+		Breakpoint() = default;
+		Breakpoint(u16 type, u32 addr) : addr(addr), type(type) { }
+		u32 addr = 0;
+		u16 type = 0;
+		u16 savedOp = 0;
+	};
+
 	void doContinue(u32 pc = 1)
 	{
 		if (pc != 1)
 			Sh4cntx.pc = pc;
-		dc_resume();
+		emu.start();
 	}

 	void step()
 	{
-		bool restoreBreakpoint = removeMatchpoint(0, Sh4cntx.pc, 2);
+		bool restoreBreakpoint = removeMatchpoint(Breakpoint::BP_TYPE_SOFTWARE_BREAK, Sh4cntx.pc, 2);
 		u32 savedPc = Sh4cntx.pc;
-		dc_step();
+		emu.step();
 		if (restoreBreakpoint)
-			insertMatchpoint(0, savedPc, 2);
+			insertMatchpoint(Breakpoint::BP_TYPE_SOFTWARE_BREAK, savedPc, 2);
+	}
+
+	void stepRange(u32 from, u32 to)
+	{
+		bool restoreBreakpoint = removeMatchpoint(Breakpoint::BP_TYPE_SOFTWARE_BREAK, Sh4cntx.pc, 2);
+		u32 savedPc = Sh4cntx.pc;
+		emu.stepRange(from, to);
+		if (restoreBreakpoint)
+			insertMatchpoint(Breakpoint::BP_TYPE_SOFTWARE_BREAK, savedPc, 2);
 	}

 	int readAllRegs(u32 **regs)
@@ -190,31 +217,31 @@ public:
 			}
 		}
 	}
-	bool insertMatchpoint(char type, u32 addr, u32 len)
+	bool insertMatchpoint(Breakpoint::Type type, u32 addr, u32 len)
 	{
-		if (type == 0 && len != 2) {
+		if (type == Breakpoint::BP_TYPE_SOFTWARE_BREAK && len != 2) {
 			WARN_LOG(COMMON, "insertMatchpoint: length != 2: %d", len);
 			return false;
 		}
 		// TODO other matchpoint types
-		if (breakpoints.find(addr) != breakpoints.end())
+		if (breakpoints[type].find(addr) != breakpoints[type].end())
 			return true;
-		breakpoints[addr] = Breakpoint(type, addr);
-		breakpoints[addr].savedOp = ReadMem16_nommu(addr);
+		breakpoints[type][addr] = Breakpoint(type, addr);
+		breakpoints[type][addr].savedOp = ReadMem16_nommu(addr);
 		WriteMem16_nommu(addr, 0xC308);	// trapa #0x20
 		return true;
 	}
-	bool removeMatchpoint(char type, u32 addr, u32 len)
+	bool removeMatchpoint(Breakpoint::Type type, u32 addr, u32 len)
 	{
-		if (type == 0 && len != 2) {
+		if (type == Breakpoint::BP_TYPE_SOFTWARE_BREAK && len != 2) {
 			WARN_LOG(COMMON, "removeMatchpoint: length != 2: %d", len);
 			return false;
 		}
-		auto it = breakpoints.find(addr);
-		if (it == breakpoints.end())
+		auto it = breakpoints[type].find(addr);
+		if (it == breakpoints[type].end())
 			return false;
 		WriteMem16_nommu(addr, it->second.savedOp);
-		breakpoints.erase(it);
+		breakpoints[type].erase(it);
 		return true;
 	}

@@ -222,7 +249,7 @@ public:
 	{
 		config::DynarecEnabled = false;
 		exception = SIGINT;
-		dc_stop();
+		emu.stop();
 		return exception;
 	}

@@ -236,7 +263,7 @@ public:
 	void postDebugTrap()
 	{
 		// needed to join the emu thread since debugTrap() is called by it
-		dc_stop();
+		emu.stop();
 	}

 	u32 currentException()
@@ -246,14 +273,14 @@ public:

 	void restart()
 	{
-		dc_stop();
-		dc_reset(true);
-		dc_resume();
+		emu.unloadGame();
+		emu.loadGame(settings.content.path.c_str());
+		emu.start();
 	}

 	void detach()
 	{
-		dc_resume();
+		emu.start();
 	}

 	void kill()
@@ -295,7 +322,10 @@ public:
 	{
 		verify(!Sh4cntx.CpuRunning);
 		size = stack.size() * 8;
-		return (const u32 *)&stack[0];
+		if (!stack.empty())
+			return (const u32 *)&stack[0];
+		else
+			return nullptr;
 	}

 	void subroutineCall()
@@ -312,13 +342,6 @@ public:

 	u32 exception = 0;

-	struct Breakpoint {
-		Breakpoint() = default;
-		Breakpoint(u16 type, u32 addr) : addr(addr), type(type) { }
-		u32 addr = 0;
-		u16 type = 0;
-		u16 savedOp = 0;
-	};
-	std::map<u32, Breakpoint> breakpoints;
+	std::map<u32, Breakpoint> breakpoints[Breakpoint::Type::BP_TYPE_COUNT];
 	std::vector<std::pair<u32, u32>> stack;
 };
@@ -22,16 +22,18 @@
 #include "gdb_server.h"
 #include "debug_agent.h"
 #include "network/net_platform.h"
+#include "cfg/option.h"
 #include <stdexcept>
 #include <thread>
 #include <chrono>
 #include <mutex>
+#include <cassert>

-#define SERVER_PORT 3263
+#define MAX_PACKET_LEN 4096

 namespace debugger {

-static void emuEventCallback(Event event);
+static void emuEventCallback(Event event, void *);

 class GdbServer
 {
@@ -40,7 +42,7 @@ public:
 		Error(const char *reason) : std::runtime_error(reason) {}
 	};

-	void init()
+	void init(int port)
 	{
 		if (VALID(serverSocket))
 			return;
@@ -55,7 +57,7 @@ public:
 		struct sockaddr_in serveraddr;
 		memset(&serveraddr, 0, sizeof(serveraddr));
 		serveraddr.sin_family = AF_INET;
-		serveraddr.sin_port = htons(SERVER_PORT);
+		serveraddr.sin_port = htons(port);

 		if (::bind(serverSocket, (struct sockaddr *)&serveraddr, sizeof(serveraddr)) < 0)
 		{
@@ -69,10 +71,16 @@ public:
 		}
 		EventManager::listen(Event::Resume, emuEventCallback);
 		EventManager::listen(Event::Terminate, emuEventCallback);
+
+		initialised = true;
 	}

 	void term()
 	{
+		if (!initialised)
+			return;
+		EventManager::unlisten(Event::Resume, emuEventCallback);
+		EventManager::unlisten(Event::Terminate, emuEventCallback);
 		stop();
 		if (VALID(clientSocket))
 		{
@@ -88,12 +96,21 @@ public:

 	void run()
 	{
+		if (!initialised || thread.joinable())
+			return;
 		DEBUG_LOG(COMMON, "GdbServer starting");
 		thread = std::thread(&GdbServer::serverThread, this);
+		if (config::GDBWaitForConnection)
+		{
+			DEBUG_LOG(COMMON, "Waiting for GDB connection...");
+			agentInterrupt();
+		}
 	}

 	void stop()
 	{
+		if (!initialised)
+			return;
 		if (thread.joinable())
 		{
 			DEBUG_LOG(COMMON, "GdbServer stopping");
@@ -104,7 +121,7 @@ public:
 	}

 	bool isRunning() const {
-		return thread.joinable();
+		return initialised && thread.joinable();
 	}

 	// called on the emu thread
@@ -181,18 +198,22 @@ private:
 		{
 			NOTICE_LOG(NETWORK, "gdb: client connection");
 			attached = true;
-			agent.interrupt();
+			agentInterrupt();
 		}
 	}

 	void readCommand()
 	{
-		if (postDebugTrapNeeded)
-		{
-			postDebugTrapNeeded = false;
-			agent.postDebugTrap();
-		}
-		try {
+        try {
+			if (postDebugTrapNeeded)
+			{
+				postDebugTrapNeeded = false;
+				try {
+					agent.postDebugTrap();
+				} catch (const FlycastException& e) {
+					throw Error(e.what());
+				}
+			}
 			std::string packet = recvPacket();
 			if (packet.empty())
 				return;
@@ -494,7 +515,12 @@ private:
 				const u32 *data = agent.getStack(len);
 				len /= 4;

+#if _MSC_VER // Non-const array size is a GCC extension
+				assert((len * 9 * 2 + 1) < MAX_PACKET_LEN);
+				char reply[MAX_PACKET_LEN];
+#else
 				char reply[len * 9 * 2 + 1];
+#endif
 				char *r = reply;
 				for (u32 i = 0; i < len; i++)
 				{
@@ -513,9 +539,13 @@ private:
 				sendPacket("");
 		}
 		else if (pkt.rfind("qSupported", 0) == 0)
+		{
 			// Tell the remote stub about features supported by GDB,
 			// and query the stub for features it supports
-			sendPacket("PacketSize=10000");
+			char qsupported[128];
+			snprintf(qsupported, 128, "PacketSize=%i;vContSupported+", MAX_PACKET_LEN);
+			sendPacket(qsupported);
+		}
 		else if (pkt.rfind("qSymbol:", 0) == 0)
 			// Notify the target that GDB is prepared to serve symbol lookup requests
 			sendPacket("OK");
@@ -568,11 +598,41 @@ private:
 		if (pkt.rfind("vAttach;", 0) == 0)
 			sendPacket("S05");
 		else if (pkt.rfind("vCont?", 0) == 0)
-			// not supported
-			sendPacket("vCont;s;c");
+			// supported vCont actions - (c)ontinue, (C)ontinue with signal, (s)tep, (S)tep with signal, (r)ange-step
+			sendPacket("vCont;c;C;s;S;t;r");
 		else if (pkt.rfind("vCont", 0) == 0)
-			// not supported
-			WARN_LOG(COMMON, "vCont not supported %s", pkt.c_str());
+		{
+			std::string vContCmd = pkt.substr(strlen("vCont;"));
+			switch (vContCmd[0])
+			{
+			case 'c':
+			case 'C':
+				sendContinue(vContCmd);
+				break;
+			case 's':
+				step(EXCEPT_NONE);
+				break;
+			case 'S':
+				step();
+			case 'r':
+			{
+				u32 from, to;
+				if (sscanf(vContCmd.c_str(), "r%x,%x", &from, &to) == 2)
+				{
+					stepRange(from, to);
+				}
+				else
+				{
+					WARN_LOG(COMMON, "Unsupported vCont:r format %s", pkt.c_str());
+					sendContinue("c");
+				}
+
+				break;
+			}
+			default:
+				WARN_LOG(COMMON, "vCont action not supported %s", pkt.c_str());
+			}
+		}
 		else if (pkt.rfind("vFile:", 0) == 0)
 			// not supported
 			sendPacket("");
@@ -597,11 +657,11 @@ private:
 			sendPacket("OK");
 			agent.kill();
 		}
-		else if (pkt.rfind("vMustReplyEmpty", 0) == 0)
-			// Reply empty packet
-			sendPacket("");
 		else
+		{
 			WARN_LOG(COMMON, "unknown v packet: %s", pkt.c_str());
+			sendPacket("");
+		}
 	}

 	void restart()
@@ -611,8 +671,23 @@ private:

 	void step(u32 what = 0)
 	{
-		agent.step();
-		sendPacket("S05");
+		try {
+			agent.step();
+			sendPacket("S05");
+		} catch (const FlycastException& e) {
+			throw Error(e.what());
+		}
+	}
+
+	void stepRange(u32 from, u32 to)
+	{
+		try {
+			sendPacket("OK");
+			agent.stepRange(from, to);
+			sendPacket("S05");
+		} catch (const FlycastException& e) {
+			throw Error(e.what());
+		}
 	}

 	void insertMatchpoint(const std::string& pkt)
@@ -625,22 +700,23 @@ private:
 			sendPacket("E01");
 		}
 		switch (type) {
-		    case 0:		// soft bp
-		    	if (agent.insertMatchpoint(0, addr, len))
+			case DebugAgent::Breakpoint::BP_TYPE_SOFTWARE_BREAK:		// soft bp
+		    	if (agent.insertMatchpoint(DebugAgent::Breakpoint::BP_TYPE_SOFTWARE_BREAK,
+		    			addr, len))
 		    		sendPacket("OK");
 		    	else
 		    		sendPacket("E01");
 		    	break;
-		    case 1:		// hardware bp
+		    case DebugAgent::Breakpoint::BP_TYPE_HARDWARE_BREAK:		// hardware bp
 		    	sendPacket("");
 		    	break;
-		    case 2:		// write watchpoint
+		    case DebugAgent::Breakpoint::BP_TYPE_WRITE_WATCHPOINT:	// write watchpoint
 		    	sendPacket("");
 		    	break;
-		    case 3:		// read watchpoint
+		    case DebugAgent::Breakpoint::BP_TYPE_READ_WATCHPOINT:		// read watchpoint
 		    	sendPacket("");
 		    	break;
-		    case 4:		// access watchpoint
+		    case DebugAgent::Breakpoint::BP_TYPE_ACCESS_WATCHPOINT:	// access watchpoint
 		    	sendPacket("");
 		    	break;
 		    default:
@@ -660,7 +736,8 @@ private:
 		}
 		switch (type) {
 		    case 0:		// soft bp
-		    	if (agent.removeMatchpoint(0, addr, len))
+		    	if (agent.removeMatchpoint(DebugAgent::Breakpoint::BP_TYPE_SOFTWARE_BREAK,
+		    			addr, len))
 		    		sendPacket("OK");
 		    	else
 		    		sendPacket("E01");
@@ -685,7 +762,7 @@ private:

 	void interrupt()
 	{
-		u32 signal = agent.interrupt();
+		u32 signal = agentInterrupt();
 		char s[10];
 		sprintf(s, "S%02x", signal);
 		sendPacket(s);
@@ -825,6 +902,16 @@ private:
 			throw Error("I/O error");
 	}

+	u32 agentInterrupt()
+	{
+		try {
+			return agent.interrupt();
+		} catch (const FlycastException& e) {
+			throw Error(e.what());
+		}
+	}
+
+	bool initialised = false;
 	bool stopRequested = false;
 	bool attached = false;
 	bool postDebugTrapNeeded = false;
@@ -838,9 +925,9 @@ public:

 static GdbServer gdbServer;

-void init()
+void init(int port)
 {
-	gdbServer.init();
+	gdbServer.init(port);
 }

 void term()
@@ -863,13 +950,17 @@ void subroutineReturn()
 	gdbServer.agent.subroutineReturn();
 }

-static void emuEventCallback(Event event)
+static void emuEventCallback(Event event, void *)
 {
 	switch (event)
 	{
 	case Event::Resume:
-		if (!gdbServer.isRunning())
-			gdbServer.run();
+		try {
+			if (!gdbServer.isRunning())
+				gdbServer.run();
+		} catch (const GdbServer::Error& e) {
+			ERROR_LOG(COMMON, "%s", e.what());
+		}
 		break;
 	case Event::Terminate:
 		gdbServer.stop();
@@ -23,9 +23,11 @@ namespace debugger {
 // exception thrown in response to trap
 struct Stop { };

+	static const int DEFAULT_PORT = 3263;
+
 #ifdef GDB_SERVER

-	void init();
+	void init(int port);
 	void term();
 	void run();
 	void debugTrap(u32 event);
@@ -33,7 +35,7 @@ struct Stop { };
 	void subroutineReturn();

 #else
-	static inline void init() {}
+	static inline void init(int port) {}
 	static inline void term() {}
 	static inline void run() {}
 	static inline void debugTrap(u32 event) {}
@@ -1,9 +0,0 @@
-# Defines the Chromium style for automatic reformatting.
-# https://clang.llvm.org/docs/ClangFormatStyleOptions.html
-BasedOnStyle: Chromium
-
-# This defaults to 'Auto'. Explicitly set it for a while, so that
-# 'vector<vector<int> >' in existing files gets formatted to
-# 'vector<vector<int>>'. ('Auto' means that clang-format will only use
-# 'int>>' if the file already contains at least one such instance.)
-Standard: Cpp11
@@ -1,17 +0,0 @@
-# The JSONPath filter expression used to identify which PRs to close.
-# The data filtered is the pull request data along with other metadata passed in
-# by probot.
-# See http://goessner.net/articles/JsonPath/
-# `true` will close all PRs.
-filters:
-  - true
-
-# The message to post to the closed PR.
-commentBody: |
-  Thanks for your contribution!  Unfortunately, we don't use GitHub pull
-  requests to manage code contributions to this repository.  Instead, please
-  see [README.md](../blob/master/README.md) which provides full instructions
-  on how to get involved.
-
-# Whether to add a label to the closed PR.
-addLabel: false
@@ -1,91 +0,0 @@
-# Copyright 2014 Google Inc. All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions are
-# met:
-#
-#     * Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-#     * Redistributions in binary form must reproduce the above
-# copyright notice, this list of conditions and the following disclaimer
-# in the documentation and/or other materials provided with the
-# distribution.
-#     * Neither the name of Google Inc. nor the names of its
-# contributors may be used to endorse or promote products derived from
-# this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-# Ignore other VCSs.
-.repo/
-.svn/
-
-# Ignore common compiled artifacts.
-*~
-*.dwo
-*.o
-lib*.a
-/breakpad.pc
-/breakpad-client.pc
-/src/client/linux/linux_client_unittest_shlib
-/src/client/linux/linux_dumper_unittest_helper
-/src/common/linux/google_crashdump_uploader_test
-/src/processor/microdump_stackwalk
-/src/processor/minidump_dump
-/src/processor/minidump_stackwalk
-/src/tools/linux/core2md/core2md
-/src/tools/linux/core_handler/core_handler
-/src/tools/linux/dump_syms/dump_syms
-/src/tools/linux/md2core/minidump-2-core
-/src/tools/linux/pid2md/pid2md
-/src/tools/linux/symupload/minidump_upload
-/src/tools/linux/symupload/sym_upload
-/src/tools/mac/dump_syms/dump_syms
-/src/tools/mac/dump_syms/dump_syms_mac
-
-# Ignore unit test artifacts.
-*_unittest
-*.log
-*.trs
-
-# Ignore autotools generated artifacts.
-.deps
-.dirstamp
-autom4te.cache/
-/config.cache
-config.h
-/config.log
-/config.status
-/Makefile
-stamp-h1
-
-# Ignore GYP generated Visual Studio artifacts.
-*.filters
-*.sdf
-*.sln
-*.suo
-*.vcproj
-*.vcxproj
-
-# Ignore GYP generated Makefiles
-src/Makefile
-*.Makefile
-*.target.mk
-
-# Ignore compiled Python files.
-*.pyc
-
-# Ignore directories gclient syncs.
-src/testing
-src/third_party/protobuf
-src/tools/gyp
@@ -1,34 +0,0 @@
-# Travis build integration.
-# https://docs.travis-ci.com/
-language: cpp
-
-sudo: required
-
-addons:
-  apt:
-    sources:
-      - ubuntu-toolchain-r-test
-    packages:
-      - clang
-      - gcc-4.8
-      - g++-4.8
-
-env:
-  global:
-    - secure: "FPczJ1u7FWGXOtUVf5AONeexfQDYnKRtuNs3phLwlPPAbgAlIc/WeTRSHC8DAb1T8IyPdN3Zi7cqLz0dvPol0iX1fWSfr8YdtW0ea8nUYH5ldmmp6H75FEUJUcISmYwL4WN7TldC6Hnzrlbw/0xmBH8gtAgddtBXKc9P9SwEZvM4OiFMHbMPwZEhRj+D95rfH12lgh3D16nbXGnx3rSNbHszvIxrU2VvlLo9Aa+hbmVj5CsBiNJjhDS64ie+VMTkuzcWNqLRYaGOCQ8ftKAlj/fjGfoKjPDN9dSJg9gW1FjOMPeQo93qhSc/hCmTq7sWxBJu48telinUgESdE5q/8gRf5J05ImWPntZAkC/wQkA20K7Kp/fH1CRaYXQMWKjts8c6dQZ5R4WxE4WXUo5rz573Ti9uyVTLys9whnzaib3YbqYv04irkhpgzo3rd8PF8SXpgK99ySQCcv/Dh7UQuXPpcaknOk2mBySXjQDgpQHHXDN2uUek1HEo5xit8fQuQw3TdPIZ9ZgzQ/c5/Dx6sLWAGEfVH9MN+hy6AiZnJ1JI+XF82kAf1pnf8WddHtlE7pAdWRFQt0iOj9T9esV1/o0VCJVzJLRdpKecF0sTpJxDuan6cFI0tNCkNjHFA5wJKYAvdOPAmYkqre7aIIqSOKy3Fjh9JP9CBJFy7eals9U="
-
-# TODO: Add an OS X config.
-matrix:
-  include:
-    - os: linux
-      compiler: gcc
-      env: USE_CC=gcc-4.8 USE_CXX=g++-4.8 COVERITY_SCAN=true
-    - os: linux
-      compiler: clang
-
-before_install: ./scripts/travis-checkout.sh
-script: ./scripts/travis-build.sh
-
-notifications:
-  email:
-    - [email protected]
@@ -1 +0,0 @@
-[email protected]
@@ -1,153 +0,0 @@
-cmake_minimum_required(VERSION 3.16)
-
-project(breakpad)
-
-include_directories(src)
-
-add_library(breakpad_client STATIC src/client/minidump_file_writer.cc)
-target_compile_features(breakpad_client PRIVATE c_std_11 cxx_std_11)
-
-target_sources(breakpad_client PRIVATE
-    	src/common/convert_UTF.cc
-    	src/common/convert_UTF.h
-    	src/common/md5.h
-    	src/common/md5.cc
-    	src/common/string_conversion.cc
-    	src/common/string_conversion.h)
-
-if(APPLE)
-	enable_language(OBJC)
-	set_target_properties(breakpad_client PROPERTIES
-	    FRAMEWORK TRUE
-	    FRAMEWORK_VERSION C
-	    MACOSX_FRAMEWORK_IDENTIFIER com.googlecode.google-breakpad
-	    MACOSX_FRAMEWORK_INFO_PLIST ${CMAKE_CURRENT_SOURCE_DIR}/src/client/mac/Framework/Info.plist
-	    # "current version" in semantic format in Mach-O binary file
-	    VERSION 16.4.0
-	    # "compatibility version" in semantic format in Mach-O binary file
-	    SOVERSION 1.0.0
-	    PUBLIC_HEADER src/client/mac/Framework/Breakpad.h
-	    XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "")
-	target_include_directories(breakpad_client PRIVATE
-		src/third_party/mac/include
-		src/client/apple/Framework
-		src/common/mac)
-	add_compile_definitions(HAVE_MACH_O_NLIST_H)
-	target_sources(breakpad_client PRIVATE
-		src/common/mac/MachIPC.mm
-		src/common/mac/bootstrap_compat.cc
-		src/common/mac/file_id.cc
-		src/common/mac/launch_reporter.h
-		src/common/mac/launch_reporter.cc
-		src/common/mac/macho_id.cc
-		src/common/mac/macho_utilities.cc
-		src/common/mac/macho_walker.cc
-		src/common/mac/string_utilities.cc
-
-		src/client/mac/crash_generation/crash_generation_client.h
-		src/client/mac/crash_generation/crash_generation_client.cc
-		src/client/mac/crash_generation/ConfigFile.h
-		src/client/mac/crash_generation/ConfigFile.mm
-		src/client/mac/crash_generation/Inspector.h
-		src/client/mac/crash_generation/Inspector.mm
-		src/client/mac/crash_generation/InspectorMain.mm
-		src/client/mac/crash_generation/crash_generation_server.cc
-		src/client/mac/handler/breakpad_nlist_64.cc
-		src/client/mac/handler/dynamic_images.cc
-		src/client/mac/handler/exception_handler.cc
-		src/client/mac/handler/minidump_generator.cc
-		src/client/mac/handler/protected_memory_allocator.cc
-		src/client/mac/handler/protected_memory_allocator.h
-		src/client/mac/Framework/Breakpad.h
-		src/client/mac/Framework/Breakpad.mm
-		src/client/mac/Framework/Breakpad_Prefix.pch
-		src/client/mac/Framework/OnDemandServer.h
-		src/client/mac/Framework/OnDemandServer.mm
-
-#	add_executable(dump_syms
-#		src/common/dwarf/bytereader.cc
-#		src/common/dwarf/dwarf2diehandler.cc
-#		src/common/dwarf/dwarf2reader.cc
-#		src/common/dwarf_cfi_to_module.cc
-#		src/common/dwarf_cu_to_module.cc
-#		src/common/dwarf_line_to_module.cc
-#		src/common/language.cc
-#		src/common/mac/dump_syms.mm
-#		src/common/mac/macho_reader.cc
-#		src/common/module.cc
-#		src/common/stabs_reader.cc
-#		src/common/stabs_to_module.cc
-#		src/tools/mac/dump_syms/dump_syms_tool.mm)
-	)
-
-elseif(UNIX)
-    enable_language(ASM)
-    if(ANDROID)
-		target_include_directories(breakpad_client PRIVATE src/common/android/include)
-    endif()
-    target_sources(breakpad_client PRIVATE
-        src/client/linux/crash_generation/crash_generation_client.cc
-		src/client/linux/crash_generation/crash_generation_server.cc
-        src/client/linux/dump_writer_common/thread_info.cc
-        src/client/linux/dump_writer_common/ucontext_reader.cc
-        src/client/linux/handler/exception_handler.h
-        src/client/linux/handler/exception_handler.cc
-        src/client/linux/handler/minidump_descriptor.cc
-    	src/client/linux/handler/minidump_descriptor.h
-    	src/client/linux/log/log.cc
-    	src/client/linux/log/log.h
-    	src/client/linux/microdump_writer/microdump_writer.cc
-    	src/client/linux/microdump_writer/microdump_writer.h
-		src/client/linux/minidump_writer/linux_core_dumper.cc
-		src/client/linux/minidump_writer/linux_core_dumper.h
-    	src/client/linux/minidump_writer/linux_dumper.cc
-    	src/client/linux/minidump_writer/linux_dumper.h
-    	src/client/linux/minidump_writer/linux_ptrace_dumper.cc
-    	src/client/linux/minidump_writer/linux_ptrace_dumper.h
-    	src/client/linux/minidump_writer/minidump_writer.cc
-    	src/client/linux/minidump_writer/minidump_writer.h
-    	src/client/minidump_file_writer-inl.h
-    	src/client/minidump_file_writer.h
-
-    	src/common/linux/breakpad_getcontext.S
-		src/common/linux/elf_core_dump.cc
-		src/common/linux/elf_core_dump.h
-    	src/common/linux/elfutils.cc
-    	src/common/linux/elfutils.h
-    	src/common/linux/file_id.cc
-    	src/common/linux/file_id.h
-    	src/common/linux/guid_creator.cc
-    	src/common/linux/guid_creator.h
-    	src/common/linux/linux_libc_support.cc
-    	src/common/linux/memory_mapped_file.cc
-    	src/common/linux/safe_readlink.cc)
-
-	if(NOT ANDROID)
-		add_executable(dump_syms
-			src/common/dwarf_cfi_to_module.cc
-			src/common/dwarf_cu_to_module.cc
-			src/common/dwarf_line_to_module.cc
-			src/common/dwarf_range_list_handler.cc
-			src/common/language.cc
-			src/common/module.cc
-			src/common/path_helper.cc
-			src/common/stabs_reader.cc
-			src/common/stabs_to_module.cc
-			src/common/dwarf/bytereader.cc
-			src/common/dwarf/dwarf2diehandler.cc
-			src/common/dwarf/dwarf2reader.cc
-			src/common/dwarf/elf_reader.cc
-			src/common/linux/crc32.cc
-			src/common/linux/dump_symbols.cc
-			src/common/linux/dump_symbols.h
-			src/common/linux/elf_symbols_to_module.cc
-			src/common/linux/elf_symbols_to_module.h
-			src/common/linux/elfutils.cc
-			src/common/linux/file_id.cc
-			src/common/linux/linux_libc_support.cc
-			src/common/linux/memory_mapped_file.cc
-			src/common/linux/safe_readlink.cc
-			src/tools/linux/dump_syms/dump_syms.cc)
-		target_compile_definitions(dump_syms PRIVATE HAVE_A_OUT_H)
-	endif()
-endif()
@@ -1,84 +0,0 @@
-# Copyright 2010 Google Inc. All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions are
-# met:
-#
-#     * Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-#     * Redistributions in binary form must reproduce the above
-# copyright notice, this list of conditions and the following disclaimer
-# in the documentation and/or other materials provided with the
-# distribution.
-#     * Neither the name of Google Inc. nor the names of its
-# contributors may be used to endorse or promote products derived from
-# this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-# This is used to mimic the svn:externals mechanism for gclient (both Git and
-# SVN) based checkouts of Breakpad. As such, its use is entirely optional. If
-# using a manually managed SVN checkout as opposed to a gclient managed checkout
-# you can still use the hooks mechanism for generating project files by calling
-# 'gclient runhooks' rather than 'gclient sync'.
-
-deps = {
-  # Testing libraries and utilities.
-  "src/src/testing":
-    "https://github.com/google/googletest.git" +
-      "@4fe018038f87675c083d0cfb6a6b57c274fb1753",
-
-  # Protobuf.
-  "src/src/third_party/protobuf/protobuf":
-    "https://github.com/google/protobuf.git" +
-      "@cb6dd4ef5f82e41e06179dcd57d3b1d9246ad6ac",
-
-  # GYP project generator.
-  "src/src/tools/gyp":
-    "https://chromium.googlesource.com/external/gyp/" +
-      "@324dd166b7c0b39d513026fa52d6280ac6d56770",
-
-  # Linux syscall support.
-  "src/src/third_party/lss":
-    "https://chromium.googlesource.com/linux-syscall-support/" +
-      "@e1e7b0ad8ee99a875b272c8e33e308472e897660",
-}
-
-hooks = [
-  {
-    # Keep the manifest up to date.
-    "action": ["python", "src/src/tools/python/deps-to-manifest.py",
-               "src/DEPS", "src/default.xml"],
-  },
-]
-
-hooks_os = {
-  'win': [
-    {
-      # TODO(chrisha): Fix the GYP files so that they work without
-      # --no-circular-check.
-      "pattern": ".",
-      "action": ["python",
-                 "src/src/tools/gyp/gyp_main.py",
-                 "--no-circular-check",
-                 "src/src/client/windows/breakpad_client.gyp"],
-    },
-    {
-      # XXX: this and above should all be wired into build/all.gyp ?
-      "action": ["python",
-                 "src/src/tools/gyp/gyp_main.py",
-                 "--no-circular-check",
-                 "src/src/tools/windows/tools_windows.gyp"],
-    },
-  ],
-}
@@ -1,370 +0,0 @@
-Installation Instructions
-*************************
-
-Copyright (C) 1994-1996, 1999-2002, 2004-2013 Free Software Foundation,
-Inc.
-
-   Copying and distribution of this file, with or without modification,
-are permitted in any medium without royalty provided the copyright
-notice and this notice are preserved.  This file is offered as-is,
-without warranty of any kind.
-
-Basic Installation
-==================
-
-   Briefly, the shell commands `./configure; make; make install' should
-configure, build, and install this package.  The following
-more-detailed instructions are generic; see the `README' file for
-instructions specific to this package.  Some packages provide this
-`INSTALL' file but do not implement all of the features documented
-below.  The lack of an optional feature in a given package is not
-necessarily a bug.  More recommendations for GNU packages can be found
-in *note Makefile Conventions: (standards)Makefile Conventions.
-
-   The `configure' shell script attempts to guess correct values for
-various system-dependent variables used during compilation.  It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions.  Finally, it creates a shell script `config.status' that
-you can run in the future to recreate the current configuration, and a
-file `config.log' containing compiler output (useful mainly for
-debugging `configure').
-
-   It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring.  Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.
-
-   If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release.  If you are using the cache, and at
-some point `config.cache' contains results you don't want to keep, you
-may remove or edit it.
-
-   The file `configure.ac' (or `configure.in') is used to create
-`configure' by a program called `autoconf'.  You need `configure.ac' if
-you want to change it or regenerate `configure' using a newer version
-of `autoconf'.
-
-   The simplest way to compile this package is:
-
-  1. `cd' to the directory containing the package's source code and type
-     `./configure' to configure the package for your system.
-
-     Running `configure' might take a while.  While running, it prints
-     some messages telling which features it is checking for.
-
-  2. Type `make' to compile the package.
-
-  3. Optionally, type `make check' to run any self-tests that come with
-     the package, generally using the just-built uninstalled binaries.
-
-  4. Type `make install' to install the programs and any data files and
-     documentation.  When installing into a prefix owned by root, it is
-     recommended that the package be configured and built as a regular
-     user, and only the `make install' phase executed with root
-     privileges.
-
-  5. Optionally, type `make installcheck' to repeat any self-tests, but
-     this time using the binaries in their final installed location.
-     This target does not install anything.  Running this target as a
-     regular user, particularly if the prior `make install' required
-     root privileges, verifies that the installation completed
-     correctly.
-
-  6. You can remove the program binaries and object files from the
-     source code directory by typing `make clean'.  To also remove the
-     files that `configure' created (so you can compile the package for
-     a different kind of computer), type `make distclean'.  There is
-     also a `make maintainer-clean' target, but that is intended mainly
-     for the package's developers.  If you use it, you may have to get
-     all sorts of other programs in order to regenerate files that came
-     with the distribution.
-
-  7. Often, you can also type `make uninstall' to remove the installed
-     files again.  In practice, not all packages have tested that
-     uninstallation works correctly, even though it is required by the
-     GNU Coding Standards.
-
-  8. Some packages, particularly those that use Automake, provide `make
-     distcheck', which can by used by developers to test that all other
-     targets like `make install' and `make uninstall' work correctly.
-     This target is generally not run by end users.
-
-Compilers and Options
-=====================
-
-   Some systems require unusual options for compilation or linking that
-the `configure' script does not know about.  Run `./configure --help'
-for details on some of the pertinent environment variables.
-
-   You can give `configure' initial values for configuration parameters
-by setting variables in the command line or in the environment.  Here
-is an example:
-
-     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
-
-   *Note Defining Variables::, for more details.
-
-Compiling For Multiple Architectures
-====================================
-
-   You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory.  To do this, you can use GNU `make'.  `cd' to the
-directory where you want the object files and executables to go and run
-the `configure' script.  `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.  This
-is known as a "VPATH" build.
-
-   With a non-GNU `make', it is safer to compile the package for one
-architecture at a time in the source code directory.  After you have
-installed the package for one architecture, use `make distclean' before
-reconfiguring for another architecture.
-
-   On MacOS X 10.5 and later systems, you can create libraries and
-executables that work on multiple system types--known as "fat" or
-"universal" binaries--by specifying multiple `-arch' options to the
-compiler but only a single `-arch' option to the preprocessor.  Like
-this:
-
-     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
-                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
-                 CPP="gcc -E" CXXCPP="g++ -E"
-
-   This is not guaranteed to produce working output in all cases, you
-may have to build one architecture at a time and combine the results
-using the `lipo' tool if you have problems.
-
-Installation Names
-==================
-
-   By default, `make install' installs the package's commands under
-`/usr/local/bin', include files under `/usr/local/include', etc.  You
-can specify an installation prefix other than `/usr/local' by giving
-`configure' the option `--prefix=PREFIX', where PREFIX must be an
-absolute file name.
-
-   You can specify separate installation prefixes for
-architecture-specific files and architecture-independent files.  If you
-pass the option `--exec-prefix=PREFIX' to `configure', the package uses
-PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files still use the regular prefix.
-
-   In addition, if you use an unusual directory layout you can give
-options like `--bindir=DIR' to specify different values for particular
-kinds of files.  Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.  In general, the
-default for these options is expressed in terms of `${prefix}', so that
-specifying just `--prefix' will affect all of the other directory
-specifications that were not explicitly provided.
-
-   The most portable way to affect installation locations is to pass the
-correct locations to `configure'; however, many packages provide one or
-both of the following shortcuts of passing variable assignments to the
-`make install' command line to change installation locations without
-having to reconfigure or recompile.
-
-   The first method involves providing an override variable for each
-affected directory.  For example, `make install
-prefix=/alternate/directory' will choose an alternate location for all
-directory configuration variables that were expressed in terms of
-`${prefix}'.  Any directories that were specified during `configure',
-but not in terms of `${prefix}', must each be overridden at install
-time for the entire installation to be relocated.  The approach of
-makefile variable overrides for each directory variable is required by
-the GNU Coding Standards, and ideally causes no recompilation.
-However, some platforms have known limitations with the semantics of
-shared libraries that end up requiring recompilation when using this
-method, particularly noticeable in packages that use GNU Libtool.
-
-   The second method involves providing the `DESTDIR' variable.  For
-example, `make install DESTDIR=/alternate/directory' will prepend
-`/alternate/directory' before all installation names.  The approach of
-`DESTDIR' overrides is not required by the GNU Coding Standards, and
-does not work on platforms that have drive letters.  On the other hand,
-it does better at avoiding recompilation issues, and works well even
-when some directory options were not specified in terms of `${prefix}'
-at `configure' time.
-
-Optional Features
-=================
-
-   If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
-
-   Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System).  The
-`README' should mention any `--enable-' and `--with-' options that the
-package recognizes.
-
-   For packages that use the X Window System, `configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
-
-   Some packages offer the ability to configure how verbose the
-execution of `make' will be.  For these packages, running `./configure
--enable-silent-rules' sets the default to minimal output, which can be
-overridden with `make V=1'; while running `./configure
--disable-silent-rules' sets the default to verbose, which can be
-overridden with `make V=0'.
-
-Particular systems
-==================
-
-   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU
-CC is not installed, it is recommended to use the following options in
-order to use an ANSI C compiler:
-
-     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
-
-and if that doesn't work, install pre-built binaries of GCC for HP-UX.
-
-   HP-UX `make' updates targets which have the same time stamps as
-their prerequisites, which makes it generally unusable when shipped
-generated files such as `configure' are involved.  Use GNU `make'
-instead.
-
-   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
-parse its `<wchar.h>' header file.  The option `-nodtk' can be used as
-a workaround.  If GNU CC is not installed, it is therefore recommended
-to try
-
-     ./configure CC="cc"
-
-and if that doesn't work, try
-
-     ./configure CC="cc -nodtk"
-
-   On Solaris, don't put `/usr/ucb' early in your `PATH'.  This
-directory contains several dysfunctional programs; working variants of
-these programs are available in `/usr/bin'.  So, if you need `/usr/ucb'
-in your `PATH', put it _after_ `/usr/bin'.
-
-   On Haiku, software installed for all users goes in `/boot/common',
-not `/usr/local'.  It is recommended to use the following options:
-
-     ./configure --prefix=/boot/common
-
-Specifying the System Type
-==========================
-
-   There may be some features `configure' cannot figure out
-automatically, but needs to determine by the type of machine the package
-will run on.  Usually, assuming the package is built to be run on the
-_same_ architectures, `configure' can figure that out, but if it prints
-a message saying it cannot guess the machine type, give it the
-`--build=TYPE' option.  TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name which has the form:
-
-     CPU-COMPANY-SYSTEM
-
-where SYSTEM can have one of these forms:
-
-     OS
-     KERNEL-OS
-
-   See the file `config.sub' for the possible values of each field.  If
-`config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
-
-   If you are _building_ compiler tools for cross-compiling, you should
-use the option `--target=TYPE' to select the type of system they will
-produce code for.
-
-   If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with `--host=TYPE'.
-
-Sharing Defaults
-================
-
-   If you want to set default values for `configure' scripts to share,
-you can create a site shell script called `config.site' that gives
-default values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists.  Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
-
-Defining Variables
-==================
-
-   Variables not defined in a site shell script can be set in the
-environment passed to `configure'.  However, some packages may run
-configure again during the build, and the customized values of these
-variables may be lost.  In order to avoid this problem, you should set
-them in the `configure' command line, using `VAR=value'.  For example:
-
-     ./configure CC=/usr/local2/bin/gcc
-
-causes the specified `gcc' to be used as the C compiler (unless it is
-overridden in the site shell script).
-
-Unfortunately, this technique does not work for `CONFIG_SHELL' due to
-an Autoconf limitation.  Until the limitation is lifted, you can use
-this workaround:
-
-     CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
-
-`configure' Invocation
-======================
-
-   `configure' recognizes the following options to control how it
-operates.
-
-`--help'
-`-h'
-     Print a summary of all of the options to `configure', and exit.
-
-`--help=short'
-`--help=recursive'
-     Print a summary of the options unique to this package's
-     `configure', and exit.  The `short' variant lists options used
-     only in the top level, while the `recursive' variant lists options
-     also present in any nested packages.
-
-`--version'
-`-V'
-     Print the version of Autoconf used to generate the `configure'
-     script, and exit.
-
-`--cache-file=FILE'
-     Enable the cache: use and save the results of the tests in FILE,
-     traditionally `config.cache'.  FILE defaults to `/dev/null' to
-     disable caching.
-
-`--config-cache'
-`-C'
-     Alias for `--cache-file=config.cache'.
-
-`--quiet'
-`--silent'
-`-q'
-     Do not print messages saying which checks are being made.  To
-     suppress all normal output, redirect it to `/dev/null' (any error
-     messages will still be shown).
-
-`--srcdir=DIR'
-     Look for the package's source code in directory DIR.  Usually
-     `configure' can determine that directory automatically.
-
-`--prefix=DIR'
-     Use DIR as the installation prefix.  *note Installation Names::
-     for more details, including other options available for fine-tuning
-     the installation locations.
-
-`--no-create'
-`-n'
-     Run the configure checks, but stop before creating any output
-     files.
-
-`configure' also accepts some other, not widely useful, options.  Run
-`configure --help' for more details.
@@ -1,132 +0,0 @@
-Copyright (c) 2006, Google Inc.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are
-met:
-
-    * Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-    * Redistributions in binary form must reproduce the above
-copyright notice, this list of conditions and the following disclaimer
-in the documentation and/or other materials provided with the
-distribution.
-    * Neither the name of Google Inc. nor the names of its
-contributors may be used to endorse or promote products derived from
-this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
--------------------------------------------------------------------
-
-Copyright 2001-2004 Unicode, Inc.
-
-Disclaimer
-
-This source code is provided as is by Unicode, Inc. No claims are
-made as to fitness for any particular purpose. No warranties of any
-kind are expressed or implied. The recipient agrees to determine
-applicability of information provided. If this file has been
-purchased on magnetic or optical media from Unicode, Inc., the
-sole remedy for any claim will be exchange of defective media
-within 90 days of receipt.
-
-Limitations on Rights to Redistribute This Code
-
-Unicode, Inc. hereby grants the right to freely use the information
-supplied in this file in the creation of products supporting the
-Unicode Standard, and to make copies of this file in any form
-for internal or external distribution as long as this notice
-remains attached.
-
--------------------------------------------------------------------
-
-libunwind - a platform-independent unwind library
-   Copyright (C) 2008 Google, Inc
-	Contributed by Paul Pluzhnikov <[email protected]>
-   Copyright (C) 2010 Konstantin Belousov <[email protected]>
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.  */
-
--------------------------------------------------------------------
-
-Copyright (c) 1999 Apple Computer, Inc. All rights reserved.
-
-@APPLE_LICENSE_HEADER_START@
-
-This file contains Original Code and/or Modifications of Original Code
-as defined in and that are subject to the Apple Public Source License
-Version 2.0 (the 'License'). You may not use this file except in
-compliance with the License. Please obtain a copy of the License at
-http://www.opensource.apple.com/apsl/ and read it before using this
-file.
-
-The Original Code and all software distributed under the License are
-distributed on an 'AS IS' basis, WITHOUT WARRANTY OF ANY KIND, EITHER
-EXPRESS OR IMPLIED, AND APPLE HEREBY DISCLAIMS ALL SUCH WARRANTIES,
-INCLUDING WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, QUIET ENJOYMENT OR NON-INFRINGEMENT.
-Please see the License for the specific language governing rights and
-limitations under the License.
-
-@APPLE_LICENSE_HEADER_END@
-
--------------------------------------------------------------------
-
-Copyright (c) 1989, 1993
-The Regents of the University of California.  All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
-   notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
-   notice, this list of conditions and the following disclaimer in the
-   documentation and/or other materials provided with the distribution.
-3. All advertising materials mentioning features or use of this software
-   must display the following acknowledgement:
-     This product includes software developed by the University of
-     California, Berkeley and its contributors.
-4. Neither the name of the University nor the names of its contributors
-   may be used to endorse or promote products derived from this software
-   without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
@@ -1,13 +0,0 @@
-# Sorted alphabetically.
-# Please see README.md for contact info.
-
-[email protected]
-[email protected]
-[email protected]
-[email protected]
-[email protected]
-[email protected]
-[email protected]
-[email protected]
-[email protected]
-[email protected]
@@ -1,139 +0,0 @@
-Google Breakpad for Android
-===========================
-
-This document explains how to use the Google Breakpad client library
-on Android, and later generate valid stack traces from the minidumps
-it generates.
-
-This release supports ARM, x86 and MIPS based Android systems.
-This release requires NDK release r11c or higher.
-
-I. Building the client library:
-===============================
-
-The Android client is built as a static library that you can
-link into your own Android native code. There are two ways to
-build it:
-
-I.1. Building with ndk-build:
-----------------------------
-
-If you're using the ndk-build build system, you can follow
-these simple steps:
-
-  1/ Include android/google_breakpad/Android.mk from your own
-     project's Android.mk
-
-     This can be done either directly, or using ndk-build's
-     import-module feature.
-
-  2/ Link the library to one of your modules by using:
-
-     LOCAL_STATIC_LIBRARIES += breakpad_client
-
-NOTE: The client library requires a C++ STL implementation,
-      which you can select with APP_STL in your Application.mk
-
-      It has been tested succesfully with both STLport and GNU libstdc++
-
-
-I.2. Building with a standalone Android toolchain:
--------------------------------------------------
-
-All you need to do is configure your build with the right 'host'
-value, and disable the processor and tools, as in:
-
-  $GOOGLE_BREAKPAD_PATH/configure --host=arm-linux-androideabi \
-                                  --disable-processor \
-                                  --disable-tools
-  make -j4
-
-The library will be under src/client/linux/libbreakpad_client.a
-
-You can also use 'make check' to run the test suite on a connected
-Android device. This requires the Android 'adb' tool to be in your
-path.
-
-II. Using the client library in Android:
-========================================
-
-The usage instructions are very similar to the Linux ones that are
-found at https://chromium.googlesource.com/breakpad/breakpad/+/master/docs/linux_starter_guide.md
-
-1/ You need to include "client/linux/handler/exception_handler.h" from a C++
-   source file.
-
-2/ If you're not using ndk-build, you also need to:
-
-   - add the following to your compiler include search paths:
-       $GOOGLE_BREAKPAD_PATH/src
-       $GOOGLE_BREAKPAD_PATH/src/common/android/include
-
-   - add -llog to your linker flags
-
-   Note that ndk-build does that for your automatically.
-
-3/ Keep in mind that there is no /tmp directory on Android.
-
-   If you use the library from a regular Android applications, specify a
-   path under your app-specific storage directory. An alternative is to
-   store them on the SDCard, but this requires a specific permission.
-
-For a concrete example, see the sample test application under
-android/sample_app. See its README for more information.
-
-
-III. Getting a stack trace on the host:
-=======================================
-
-This process is similar to other platforms, but here's a quick example:
-
-1/ Retrieve the minidumps on your development machine.
-
-2/ Dump the symbols for your native libraries with the 'dump_syms' tool.
-   This first requires building the host version of Google Breakpad, then
-   calling:
-
-      dump_syms $PROJECT_PATH/obj/local/$ABI/libfoo.so > libfoo.so.sym
-
-3/ Create the symbol directory hierarchy.
-
-   The first line of the generated libfoo.so.sym will have a "MODULE"
-   entry that carries a hexadecimal version number, e.g.:
-
-     MODULE Linux arm D51B4A5504974FA6ECC1869CAEE3603B0 test_google_breakpad
-
-   Note: The second field could be either 'Linux' or 'Android'.
-
-   Extract the version number, and a 'symbol' directory, for example:
-
-      $PROJECT_PATH/symbols/libfoo.so/$VERSION/
-
-   Copy/Move your libfoo.sym file there.
-
-4/ Invoke minidump_stackwalk to create the stack trace:
-
-     minidump_stackwalk $MINIDUMP_FILE $PROJECT_PATH/symbols
-
-Note that various helper scripts can be found on the web to automate these
-steps.
-
-IV. Verifying the Android build library:
-========================================
-
-If you modify Google Breakpad and want to check that it still works correctly
-on Android, please run the android/run-checks.sh script which will do all
-necessary verifications for you. This includes:
-
-  - Rebuilding the full host binaries.
-  - Rebuilding the full Android binaries with configure/make.
-  - Rebuilding the client library unit tests, and running them on a device.
-  - Rebuilding the client library with ndk-build.
-  - Building, installing and running a test crasher program on a device.
-  - Extracting the corresponding minidump, dumping the test program symbols
-    and generating a stack trace.
-  - Checking the generated stack trace for valid source locations.
-
-For more details, please run:
-
-  android/run-checks.sh --help-all
@@ -1,82 +0,0 @@
-# Breakpad
-
-Breakpad is a set of client and server components which implement a
-crash-reporting system.
-
-* [Homepage](https://chromium.googlesource.com/breakpad/breakpad/)
-* [Documentation](./docs/)
-* [Bugs](https://bugs.chromium.org/p/google-breakpad/)
-* Discussion/Questions: [[email protected]](https://groups.google.com/d/forum/google-breakpad-discuss)
-* Developer/Reviews: [[email protected]](https://groups.google.com/d/forum/google-breakpad-dev)
-* Tests: [![Build Status](https://travis-ci.org/google/breakpad.svg?branch=main)](https://travis-ci.org/google/breakpad) [![Build status](https://ci.appveyor.com/api/projects/status/eguv4emv2rhq68u2?svg=true)](https://ci.appveyor.com/project/vapier/breakpad)
-* Coverage [![Coverity Status](https://scan.coverity.com/projects/9215/badge.svg)](https://scan.coverity.com/projects/google-breakpad)
-
-## Getting started (from main)
-
-1.  First, [download depot_tools](http://dev.chromium.org/developers/how-tos/install-depot-tools)
-    and ensure that they’re in your `PATH`.
-
-2.  Create a new directory for checking out the source code (it must be named
-    breakpad).
-
-    ```sh
-    mkdir breakpad && cd breakpad
-    ```
-
-3.  Run the `fetch` tool from depot_tools to download all the source repos.
-
-    ```sh
-    fetch breakpad
-    cd src
-    ```
-
-4.  Build the source.
-
-    ```sh
-    ./configure && make
-    ```
-
-    You can also cd to another directory and run configure from there to build
-    outside the source tree.
-
-    This will build the processor tools (`src/processor/minidump_stackwalk`,
-    `src/processor/minidump_dump`, etc), and when building on Linux it will
-    also build the client libraries and some tools
-    (`src/tools/linux/dump_syms/dump_syms`,
-    `src/tools/linux/md2core/minidump-2-core`, etc).
-
-5.  Optionally, run tests.
-
-    ```sh
-    make check
-    ```
-
-6.  Optionally, install the built libraries
-
-    ```sh
-    make install
-    ```
-
-If you need to reconfigure your build be sure to run `make distclean` first.
-
-To update an existing checkout to a newer revision, you can
-`git pull` as usual, but then you should run `gclient sync` to ensure that the
-dependent repos are up-to-date.
-
-## To request change review
-
-1.  Follow the steps above to get the source and build it.
-
-2.  Make changes. Build and test your changes.
-    For core code like processor use methods above.
-    For linux/mac/windows, there are test targets in each project file.
-
-3.  Commit your changes to your local repo and upload them to the server.
-    http://dev.chromium.org/developers/contributing-code
-    e.g. `git commit ... && git cl upload ...`
-    You will be prompted for credential and a description.
-
-4.  At https://chromium-review.googlesource.com/ you'll find your issue listed;
-    click on it, then “Add reviewer”, and enter in the code reviewer. Depending
-    on your settings, you may not see an email, but the reviewer has been
-    notified with google-breakpad-dev@googlegroups.com always CC’d.
@@ -1,372 +0,0 @@
-# Copyright (c) 2012 Google Inc.
-# All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions are
-# met:
-#
-#     * Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-#     * Redistributions in binary form must reproduce the above
-# copyright notice, this list of conditions and the following disclaimer
-# in the documentation and/or other materials provided with the
-# distribution.
-#     * Neither the name of Google Inc. nor the names of its
-# contributors may be used to endorse or promote products derived from
-# this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-# Collection of common shell functions for 'run-checks.sh' et 'test-shell.sh'
-
-# All internal variables and functions use an underscore as a prefix
-# (e.g. _VERBOSE, _ALL_CLEANUPS, etc..).
-
-# Sanitize the environment
-export LANG=C
-export LC_ALL=C
-
-if [ "$BASH_VERSION" ]; then
-  set -o posix
-fi
-
-# Utility functions
-
-_ALL_CLEANUPS=
-
-# Register a function to be called when the script exits, even in case of
-# Ctrl-C, logout, etc.
-# $1: function name.
-atexit () {
-  if [ -z "$_ALL_CLEANUPS" ]; then
-    _ALL_CLEANUPS=$1
-    # Ensure a clean exit when the script is:
-    #  - Exiting normally (EXIT)
-    #  - Interrupted by Ctrl-C (INT)
-    #  - Interrupted by log out (HUP)
-    #  - Being asked to quit nicely (TERM)
-    #  - Being asked to quit and dump core (QUIT)
-    trap "_exit_cleanups \$?" EXIT INT HUP QUIT TERM
-  else
-    _ALL_CLEANUPS="$_ALL_CLEANUPS $1"
-  fi
-}
-
-# Called on exit if at least one function was registered with atexit
-# $1: final exit status code
-_exit_cleanups () {
-  local CLEANUP CLEANUPS
-  # Ignore calls to atexit during cleanups
-  CLEANUPS=$_ALL_CLEANUPS
-  _ALL_CLEANUPS=
-  for CLEANUP in $CLEANUPS; do
-    ($CLEANUP)
-  done
-  exit "$@"
-}
-
-
-
-
-# Dump a panic message then exit.
-# $1+: message
-panic () {
-  echo "ERROR: $@" >&2
-  exit 1
-}
-
-# If the previous command failed, dump a panic message then exit.
-# $1+: message.
-fail_panic () {
-  if [ $? != 0 ]; then
-    panic "$@"
-  fi;
-}
-
-_VERBOSE=0
-
-# Increase verbosity for dump/log/run/run2 functions
-increase_verbosity () {
-  _VERBOSE=$(( $_VERBOSE + 1 ))
-}
-
-# Decrease verbosity
-decrease_verbosity () {
-  _VERBOSE=$(( $_VERBOSE - 1 ))
-}
-
-# Returns success iff verbosity level is higher than a specific value
-# $1: verbosity level
-verbosity_is_higher_than () {
-  [ "$_VERBOSE" -gt "$1" ]
-}
-
-# Returns success iff verbosity level is lower than a specific value
-# $1: verbosity level
-verbosity_is_lower_than () {
-  [ "$_VERBOSE" -le "$1" ]
-}
-
-# Dump message to stdout, unless verbosity is < 0, i.e. --quiet was called
-# $1+: message
-dump () {
-  if [ "$_VERBOSE" -ge 0 ]; then
-    printf "%s\n" "$*"
-  fi
-}
-
-# If --verbose was used, dump a message to stdout.
-# $1+: message
-log () {
-  if [ "$_VERBOSE" -ge 1 ]; then
-    printf "%s\n" "$*"
-  fi
-}
-
-_RUN_LOG=
-
-# Set a run log file that can be used to collect the output of commands that
-# are not displayed.
-set_run_log () {
-  _RUN_LOG=$1
-}
-
-# Run a command. Output depends on $_VERBOSE:
-#   $_VERBOSE <= 0:  Run command, store output into the run log
-#   $_VERBOSE >= 1:  Dump command, run it, output goest to stdout
-# Note: Ideally, the command's output would go to the run log for $_VERBOSE >= 1
-#       but the 'tee' tool doesn't preserve the status code of its input pipe
-#       in case of error.
-run () {
-  local LOGILE
-  if [ "$_RUN_LOG" ]; then
-    LOGFILE=$_RUN_LOG
-  else
-    LOGFILE=/dev/null
-  fi
-
-  if [ "$_VERBOSE" -ge 1 ]; then
-    echo "COMMAND: $@"
-    "$@"
-  else
-    "$@" >>$LOGFILE 2>&1
-  fi
-}
-
-# Same as run(), but only dump command output for $_VERBOSE >= 2
-run2 () {
-  local LOGILE
-  if [ "$_RUN_LOG" ]; then
-    LOGFILE=$_RUN_LOG
-  else
-    LOGFILE=/dev/null
-  fi
-
-  if [ "$_VERBOSE" -ge 1 ]; then
-    echo "COMMAND: $@"
-  fi
-  if [ "$_VERBOSE" -ge 2 ]; then
-    "$@"
-  else
-    "$@" >>$LOGFILE 2>&1
-  fi
-}
-
-# Extract number of cores to speed up the builds
-# Out: number of CPU cores
-get_core_count () {
-  case $(uname -s) in
-    Linux)
-      grep -c -e '^processor' /proc/cpuinfo
-      ;;
-    Darwin)
-      sysctl -n hw.ncpu
-      ;;
-    CYGWIN*|*_NT-*)
-      echo $NUMBER_OF_PROCESSORS
-      ;;
-    *)
-      echo 1
-      ;;
-  esac
-}
-
-
-# Check for the Android ADB program.
-#
-# On success, return nothing, but updates internal variables so later calls to
-# adb_shell, adb_push, etc.. will work. You can get the path to the ADB program
-# with adb_get_program if needed.
-#
-# On failure, returns 1, and updates the internal adb error message, which can
-# be retrieved with adb_get_error.
-#
-# $1: optional ADB program path.
-# Return: success or failure.
-_ADB=
-_ADB_STATUS=
-_ADB_ERROR=
-
-adb_check () {
-  # First, try to find the executable in the path, or the SDK install dir.
-  _ADB=$1
-  if [ -z "$_ADB" ]; then
-    _ADB=$(which adb 2>/dev/null)
-    if [ -z "$_ADB" -a "$ANDROID_SDK_ROOT" ]; then
-      _ADB=$ANDROID_SDK_ROOT/platform-tools/adb
-      if [ ! -f "$_ADB" ]; then
-        _ADB=
-      fi
-    fi
-    if [ -z "$_ADB" ]; then
-      _ADB_STATUS=1
-      _ADB_ERROR="The Android 'adb' tool is not in your path."
-      return 1
-    fi
-  fi
-
-  log "Found ADB program: $_ADB"
-
-  # Check that it works correctly
-  local ADB_VERSION
-  ADB_VERSION=$("$_ADB" version 2>/dev/null)
-  case $ADB_VERSION in
-    "Android Debug Bridge "*) # Pass
-      log "Found ADB version: $ADB_VERSION"
-      ;;
-    *) # Fail
-      _ADB_ERROR="Your ADB binary reports a bad version ($ADB_VERSION): $_ADB"
-      _ADB_STATUS=1
-      return 1
-  esac
-
-  _ADB_STATUS=0
-  return 0
-}
-
-
-# Return the path to the Android ADB program, if correctly detected.
-# On failure, return the empty string.
-# Out: ADB program path (or empty on failure)
-# Return: success or failure.
-adb_get_program () {
-  # Return cached value as soon as possible.
-  if [ -z "$_ADB_STATUS" ]; then
-    adb_check $1
-  fi
-  echo "$_ADB"
-  return $_ADB_STATUS
-}
-
-# Return the error corresponding to the last ADB function failure.
-adb_get_error () {
-  echo "$_ADB_ERROR"
-}
-
-# Check that there is one device connected through ADB.
-# In case of failure, use adb_get_error to know why this failed.
-# $1: Optional adb program path
-# Return: success or failure.
-_ADB_DEVICE=
-_ADB_DEVICE_STATUS=
-adb_check_device () {
-  if [ "$_ADB_DEVICE_STATUS" ]; then
-    return $_ADB_DEVICE_STATUS
-  fi
-
-  # Check for ADB.
-  if ! adb_check $1; then
-    _ADB_DEVICE_STATUS=$_ADB_STATUS
-    return 1
-  fi
-
-  local ADB_DEVICES NUM_DEVICES FINGERPRINT
-
-  # Count the number of connected devices.
-  ADB_DEVICES=$("$_ADB" devices 2>/dev/null | awk '$2 == "device" { print $1; }')
-  NUM_DEVICES=$(echo "$ADB_DEVICES" | wc -l)
-  case $NUM_DEVICES in
-    0)
-      _ADB_ERROR="No Android device connected. Please connect one to your machine."
-      _ADB_DEVICE_STATUS=1
-      return 1
-      ;;
-    1) # Pass
-      # Ensure the same device will be called in later adb_shell calls.
-      export ANDROID_SERIAL=$ADB_DEVICES
-      ;;
-    *) # 2 or more devices.
-      if [ "$ANDROID_SERIAL" ]; then
-        ADB_DEVICES=$ANDROID_SERIAL
-        NUM_DEVICES=1
-      else
-        _ADB_ERROR="More than one Android device connected. \
-Please define ANDROID_SERIAL in your environment"
-        _ADB_DEVICE_STATUS=1
-        return 1
-      fi
-      ;;
-  esac
-
-  _ADB_DEVICE_STATUS=0
-  _ADB_DEVICE=$ADB_DEVICES
-
-  FINGERPRINT=$(adb_shell getprop ro.build.fingerprint)
-  log "Using ADB device: $ANDROID_SERIAL ($FINGERPRINT)"
-  return 0
-}
-
-# The 'adb shell' command is pretty hopeless, try to make sense of it by:
-#   1/ Removing trailing \r from line endings.
-#   2/ Ensuring the function returns the command's status code.
-#
-# $1+: Command
-# Out: command output (stdout + stderr combined)
-# Return: command exit status
-adb_shell () {
-  local RET ADB_LOG
-  # Check for ADB device.
-  adb_check_device || return 1
-  ADB_LOG=$(mktemp "${TMPDIR:-/tmp}/adb-XXXXXXXX")
-  "$_ADB" shell "$@" ";" echo \$? > "$ADB_LOG" 2>&1
-  sed -i -e 's![[:cntrl:]]!!g' "$ADB_LOG"  # Remove \r.
-  RET=$(sed -e '$!d' "$ADB_LOG")           # Last line contains status code.
-  sed -e '$d' "$ADB_LOG"                   # Print everything except last line.
-  rm -f "$ADB_LOG"
-  return $RET
-}
-
-# Push a file to a device.
-# $1: source file path
-# $2: device target file path
-# Return: success or failure.
-adb_push () {
-  adb_check_device || return 1
-  run "$_ADB" push "$1" "$2"
-}
-
-# Pull a file from a device
-# $1: device file path
-# $2: target host file path
-# Return: success or failure.
-adb_pull () {
-  adb_check_device || return 1
-  run "$_ADB" pull "$1" "$2"
-}
-
-# Same as adb_push, but will panic if the operations didn't succeed.
-adb_install () {
-  adb_push "$@"
-  fail_panic "Failed to install $1 to the Android device at $2"
-}
-
@@ -1,104 +0,0 @@
-# Copyright (c) 2012, Google Inc.
-# All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions are
-# met:
-#
-#     * Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-#     * Redistributions in binary form must reproduce the above
-# copyright notice, this list of conditions and the following disclaimer
-# in the documentation and/or other materials provided with the
-# distribution.
-#     * Neither the name of Google Inc. nor the names of its
-# contributors may be used to endorse or promote products derived from
-# this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-# ndk-build module definition for the Google Breakpad client library
-#
-# To use this file, do the following:
-#
-#   1/ Include this file from your own Android.mk, either directly
-#      or with through the NDK's import-module function.
-#
-#   2/ Use the client static library in your project with:
-#
-#      LOCAL_STATIC_LIBRARIES += breakpad_client
-#
-#   3/ In your source code, include "src/client/linux/exception_handler.h"
-#      and use the Linux instructions to use it.
-#
-# This module works with either the STLport or GNU libstdc++, but you need
-# to select one in your Application.mk
-#
-
-# The top Google Breakpad directory.
-# We assume this Android.mk to be under 'android/google_breakpad'
-
-LOCAL_PATH := $(call my-dir)/../..
-
-# Defube the client library module, as a simple static library that
-# exports the right include path / linker flags to its users.
-
-include $(CLEAR_VARS)
-
-LOCAL_MODULE := breakpad_client
-
-LOCAL_CPP_EXTENSION := .cc
-
-# Breakpad uses inline ARM assembly that requires the library
-# to be built in ARM mode. Otherwise, the build will fail with
-# cryptic assembler messages like:
-#   Compile++ thumb  : google_breakpad_client <= crash_generation_client.cc
-#   /tmp/cc8aMSoD.s: Assembler messages:
-#   /tmp/cc8aMSoD.s:132: Error: invalid immediate: 288 is out of range
-#   /tmp/cc8aMSoD.s:244: Error: invalid immediate: 296 is out of range
-LOCAL_ARM_MODE := arm
-
-# List of client source files, directly taken from Makefile.am
-LOCAL_SRC_FILES := \
-    src/client/linux/crash_generation/crash_generation_client.cc \
-    src/client/linux/dump_writer_common/thread_info.cc \
-    src/client/linux/dump_writer_common/ucontext_reader.cc \
-    src/client/linux/handler/exception_handler.cc \
-    src/client/linux/handler/minidump_descriptor.cc \
-    src/client/linux/log/log.cc \
-    src/client/linux/microdump_writer/microdump_writer.cc \
-    src/client/linux/minidump_writer/linux_dumper.cc \
-    src/client/linux/minidump_writer/linux_ptrace_dumper.cc \
-    src/client/linux/minidump_writer/minidump_writer.cc \
-    src/client/minidump_file_writer.cc \
-    src/common/convert_UTF.cc \
-    src/common/md5.cc \
-    src/common/string_conversion.cc \
-    src/common/linux/breakpad_getcontext.S \
-    src/common/linux/elfutils.cc \
-    src/common/linux/file_id.cc \
-    src/common/linux/guid_creator.cc \
-    src/common/linux/linux_libc_support.cc \
-    src/common/linux/memory_mapped_file.cc \
-    src/common/linux/safe_readlink.cc
-
-LOCAL_C_INCLUDES        := $(LOCAL_PATH)/src/common/android/include \
-                           $(LOCAL_PATH)/src \
-                           $(LSS_PATH)
-
-LOCAL_EXPORT_C_INCLUDES := $(LOCAL_C_INCLUDES)
-LOCAL_EXPORT_LDLIBS     := -llog
-
-include $(BUILD_STATIC_LIBRARY)
-
-# Done.
@@ -1,555 +0,0 @@
-#!/bin/sh
-# Copyright (c) 2012 Google Inc.
-# All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions are
-# met:
-#
-#     * Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-#     * Redistributions in binary form must reproduce the above
-# copyright notice, this list of conditions and the following disclaimer
-# in the documentation and/or other materials provided with the
-# distribution.
-#     * Neither the name of Google Inc. nor the names of its
-# contributors may be used to endorse or promote products derived from
-# this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-# Sanitize the environment
-export LANG=C
-export LC_ALL=C
-
-if [ "$BASH_VERSION" ]; then
-  set -o posix
-fi
-
-PROGDIR=$(dirname "$0")
-PROGDIR=$(cd "$PROGDIR" && pwd)
-PROGNAME=$(basename "$0")
-
-. $PROGDIR/common-functions.sh
-
-DEFAULT_ABI="armeabi"
-VALID_ABIS="armeabi armeabi-v7a x86 mips"
-
-ABI=
-ADB=
-ALL_TESTS=
-ENABLE_M32=
-HELP=
-HELP_ALL=
-NDK_DIR=
-NO_CLEANUP=
-NO_DEVICE=
-NUM_JOBS=$(get_core_count)
-TMPDIR=
-
-for opt do
-  # The following extracts the value if the option is like --name=<value>.
-  optarg=$(expr -- $opt : '^--[^=]*=\(.*\)$')
-  case $opt in
-    --abi=*) ABI=$optarg;;
-    --adb=*) ADB=$optarg;;
-    --all-tests) ALL_TESTS=true;;
-    --enable-m32) ENABLE_M32=true;;
-    --help|-h|-?) HELP=TRUE;;
-    --help-all) HELP_ALL=true;;
-    --jobs=*) NUM_JOBS=$optarg;;
-    --ndk-dir=*) NDK_DIR=$optarg;;
-    --tmp-dir=*) TMPDIR=$optarg;;
-    --no-cleanup) NO_CLEANUP=true;;
-    --no-device) NO_DEVICE=true;;
-    --quiet) decrease_verbosity;;
-    --verbose) increase_verbosity;;
-    -*) panic "Invalid option '$opt', see --help for details.";;
-    *) panic "This script doesn't take any parameters. See --help for details."
-       ;;
-  esac
-done
-
-if [ "$HELP" -o "$HELP_ALL" ]; then
-  echo "\
-  Usage: $PROGNAME [options]
-
-  This script is used to check that your Google Breakpad source tree can
-  be properly built for Android, and that the client library and host tools
-  work properly together.
-"
-  if [ "$HELP_ALL" ]; then
-    echo "\
-  In more details, this script will:
-
-  - Rebuild the host version of Google Breakpad in a temporary
-    directory (with the Auto-tools based build system).
-
-  - Rebuild the Android client library with the Google Breakpad build
-    system (using autotools/configure). This requires that you define
-    ANDROID_NDK_ROOT in your environment to point to a valid Android NDK
-    installation directory, or use the --ndk-dir=<path> option.
-
-  - Rebuild the Android client library and a test crashing program with the
-    Android NDK build system (ndk-build).
-
-  - Require an Android device connected to your machine, and the 'adb'
-    tool in your path. They are used to:
-
-      - Install and  run a test crashing program.
-      - Extract the corresponding minidump from the device.
-      - Dump the symbols from the test program on the host with 'dump_syms'
-      - Generate a stack trace with 'minidump_stackwalk'
-      - Check the stack trace content for valid source file locations.
-
-    You can however skip this requirement and only test the builds by using
-    the --no-device flag.
-
-    By default, all generated files will be created in a temporary directory
-    that is removed when the script completion. If you want to inspect the
-    files, use the --no-cleanup option.
-
-    Finally, use --verbose to increase the verbosity level, this will help
-    you see which exact commands are being issues and their result. Use the
-    flag twice for even more output. Use --quiet to decrease verbosity
-    instead and run the script silently.
-
-    If you have a device connected, the script will probe it to determine
-    its primary CPU ABI, and build the test program for it. You can however
-    use the --abi=<name> option to override this (this can be useful to check
-    the secondary ABI, e.g. using --abi=armeabi to check that such a program
-    works correctly on an ARMv7-A device).
-
-    If you don't have a device connected, the test program will be built (but
-    not run) with the default '$DEFAULT_ABI' ABI. Again, you can use
-    --abi=<name> to override this. Valid ABI names are:
-
-        $VALID_ABIS
-
-    The script will only run the client library unit test on the device
-    by default. You can use --all-tests to also build and run the unit
-    tests for the Breakpad tools and processor, but be warned that this
-    adds several minutes of testing time. --all-tests will also run the
-    host unit tests suite.
-"
-
-  fi  # HELP_ALL
-
-  echo "\
-  Valid options:
-
-      --help|-h|-?     Display this message.
-      --help-all       Display extended help.
-      --enable-m32     Build 32-bit version of host tools.
-      --abi=<name>     Specify target CPU ABI [auto-detected].
-      --jobs=<count>   Run <count> build tasks in parallel [$NUM_JOBS].
-      --ndk-dir=<path> Specify NDK installation directory.
-      --tmp-dir=<path> Specify temporary directory (will be wiped-out).
-      --adb=<path>     Specify adb program path.
-      --no-cleanup     Don't remove temporary directory after completion.
-      --no-device      Do not try to detect devices, nor run crash test.
-      --all-tests      Run all unit tests (i.e. tools and processor ones too).
-      --verbose        Increase verbosity.
-      --quiet          Decrease verbosity."
-
-  exit 0
-fi
-
-TESTAPP_DIR=$PROGDIR/sample_app
-
-# Select NDK install directory.
-if [ -z "$NDK_DIR" ]; then
-  if [ -z "$ANDROID_NDK_ROOT" ]; then
-    panic "Please define ANDROID_NDK_ROOT in your environment, or use \
--ndk-dir=<path>."
-  fi
-  NDK_DIR="$ANDROID_NDK_ROOT"
-  log "Found NDK directory: $NDK_DIR"
-else
-  log "Using NDK directory: $NDK_DIR"
-fi
-# Small sanity check.
-NDK_BUILD="$NDK_DIR/ndk-build"
-if [ ! -f "$NDK_BUILD" ]; then
-  panic "Your NDK directory is not valid (missing ndk-build): $NDK_DIR"
-fi
-
-# Ensure the temporary directory is deleted on exit, except if the --no-cleanup
-# option is used.
-
-clean_tmpdir () {
-  if [ "$TMPDIR" ]; then
-    if [ -z "$NO_CLEANUP" ]; then
-      log "Cleaning up: $TMPDIR"
-      rm -rf "$TMPDIR"
-    else
-      dump "Temporary directory contents preserved: $TMPDIR"
-    fi
-  fi
-  exit "$@"
-}
-
-atexit clean_tmpdir
-
-# If --tmp-dir=<path> is not used, create a temporary directory.
-# Otherwise, start by cleaning up the user-provided path.
-if [ -z "$TMPDIR" ]; then
-  TMPDIR=$(mktemp -d /tmp/$PROGNAME.XXXXXXXX)
-  fail_panic "Can't create temporary directory!"
-  log "Using temporary directory: $TMPDIR"
-else
-  if [ ! -d "$TMPDIR" ]; then
-    mkdir -p "$TMPDIR"
-    fail_panic "Can't create temporary directory: $TMPDIR"
-  else
-    log "Cleaning up temporary directory: $TMPDIR"
-    rm -rf "$TMPDIR"/*
-    fail_panic "Cannot cleanup temporary directory!"
-  fi
-fi
-
-if [ -z "$NO_DEVICE" ]; then
-  if ! adb_check_device $ADB; then
-    echo "$(adb_get_error)"
-    echo "Use --no-device to build the code without running any tests."
-    exit 1
-  fi
-fi
-
-BUILD_LOG="$TMPDIR/build.log"
-RUN_LOG="$TMPDIR/run.log"
-CRASH_LOG="$TMPDIR/crash.log"
-
-set_run_log "$RUN_LOG"
-
-TMPHOST="$TMPDIR/host-local"
-
-cd "$TMPDIR"
-
-# Build host version of the tools
-dump "Building host binaries."
-CONFIGURE_FLAGS=
-if [ "$ENABLE_M32" ]; then
-  CONFIGURE_FLAGS="$CONFIGURE_FLAGS --enable-m32"
-fi
-(
-  run mkdir "$TMPDIR/build-host" &&
-  run cd "$TMPDIR/build-host" &&
-  run2 "$PROGDIR/../configure" --prefix="$TMPHOST" $CONFIGURE_FLAGS &&
-  run2 make -j$NUM_JOBS install
-)
-fail_panic "Can't build host binaries!"
-
-if [ "$ALL_TESTS" ]; then
-  dump "Running host unit tests."
-  (
-    run cd "$TMPDIR/build-host" &&
-    run2 make -j$NUM_JOBS check
-  )
-  fail_panic "Host unit tests failed!!"
-fi
-
-TMPBIN=$TMPHOST/bin
-
-# Generate a stand-alone NDK toolchain
-
-# Extract CPU ABI and architecture from device, if any.
-if adb_check_device; then
-  DEVICE_ABI=$(adb_shell getprop ro.product.cpu.abi)
-  DEVICE_ABI2=$(adb_shell getprop ro.product.cpu.abi2)
-  if [ -z "$DEVICE_ABI" ]; then
-    panic "Can't extract ABI from connected device!"
-  fi
-  if [ "$DEVICE_ABI2" ]; then
-    dump "Found device ABIs: $DEVICE_ABI $DEVICE_ABI2"
-  else
-    dump "Found device ABI: $DEVICE_ABI"
-    DEVICE_ABI2=$DEVICE_ABI
-  fi
-
-  # If --abi=<name> is used, check that the device supports it.
-  if [ "$ABI" -a "$DEVICE_ABI" != "$ABI" -a "$DEVICE_ABI2" != "$ABI" ]; then
-    dump  "ERROR: Device ABI(s) do not match --abi command-line value ($ABI)!"
-    panic "Please use --no-device to skip device tests."
-  fi
-
-  if [ -z "$ABI" ]; then
-    ABI=$DEVICE_ABI
-    dump "Using CPU ABI: $ABI (device)"
-  else
-    dump "Using CPU ABI: $ABI (command-line)"
-  fi
-else
-  if [ -z "$ABI" ]; then
-    # No device connected, choose default ABI
-    ABI=$DEFAULT_ABI
-    dump "Using CPU ABI: $ABI (default)"
-  else
-    dump "Using CPU ABI: $ABI (command-line)"
-  fi
-fi
-
-# Check the ABI value
-VALID=
-for VALID_ABI in $VALID_ABIS; do
-  if [ "$ABI" = "$VALID_ABI" ]; then
-    VALID=true
-    break
-  fi
-done
-
-if [ -z "$VALID" ]; then
-  panic "Unknown CPU ABI '$ABI'. Valid values are: $VALID_ABIS"
-fi
-
-# Extract architecture name from ABI
-case $ABI in
-  armeabi*) ARCH=arm;;
-  *) ARCH=$ABI;;
-esac
-
-# Extract GNU configuration name
-case $ARCH in
-  arm)
-    GNU_CONFIG=arm-linux-androideabi
-    ;;
-  x86)
-    GNU_CONFIG=i686-linux-android
-    ;;
-  mips)
-    GNU_CONFIG=mipsel-linux-android
-    ;;
-  *)
-    GNU_CONFIG="$ARCH-linux-android"
-    ;;
-esac
-
-# Generate standalone NDK toolchain installation
-NDK_STANDALONE="$TMPDIR/ndk-$ARCH-toolchain"
-echo "Generating NDK standalone toolchain installation"
-mkdir -p "$NDK_STANDALONE"
-# NOTE: The --platform=android-9 is required to provide <regex.h> for GTest.
-run "$NDK_DIR/build/tools/make-standalone-toolchain.sh" \
-      --arch="$ARCH" \
-      --platform=android-9 \
-      --install-dir="$NDK_STANDALONE"
-fail_panic "Can't generate standalone NDK toolchain installation!"
-
-# Rebuild the client library, processor and tools with the auto-tools based
-# build system. Even though it's not going to be used, this checks that this
-# still works correctly.
-echo "Building full Android binaries with configure/make"
-TMPTARGET="$TMPDIR/target-local"
-(
-  PATH="$NDK_STANDALONE/bin:$PATH"
-  run mkdir "$TMPTARGET" &&
-  run mkdir "$TMPDIR"/build-target &&
-  run cd "$TMPDIR"/build-target &&
-  run2 "$PROGDIR"/../configure --prefix="$TMPTARGET" \
-                               --host="$GNU_CONFIG" &&
-  run2 make -j$NUM_JOBS install
-)
-fail_panic "Could not rebuild Android binaries!"
-
-# Build and/or run unit test suite.
-# If --no-device is used, only rebuild it, otherwise, run in on the
-# connected device.
-if [ "$NO_DEVICE" ]; then
-  ACTION="Building"
-  # This is a trick to force the Makefile to ignore running the scripts.
-  TESTS_ENVIRONMENT="TESTS_ENVIRONMENT=true"
-else
-  ACTION="Running"
-  TESTS_ENVIRONMENT=
-fi
-
-(
-  PATH="$NDK_STANDALONE/bin:$PATH"
-  run cd "$TMPDIR"/build-target &&
-  # Reconfigure to only run the client unit test suite.
-  # This one should _never_ fail.
-  dump "$ACTION Android client library unit tests."
-  run2 "$PROGDIR"/../configure --prefix="$TMPTARGET" \
-                               --host="$GNU_CONFIG" \
-                               --disable-tools \
-                               --disable-processor &&
-  run make -j$NUM_JOBS check $TESTS_ENVIRONMENT || exit $?
-
-  if [ "$ALL_TESTS" ]; then
-    dump "$ACTION Tools and processor unit tests."
-    # Reconfigure to run the processor and tools tests.
-    # Most of these fail for now, so do not worry about it.
-    run2 "$PROGDIR"/../configure --prefix="$TMPTARGET" \
-                                 --host="$GNU_CONFIG" &&
-    run make -j$NUM_JOBS check $TESTS_ENVIRONMENT
-    if [ $? != 0 ]; then
-      dump "Tools and processor unit tests failed as expected. \
-Use --verbose for results."
-    fi                           
-  fi
-)
-fail_panic "Client library unit test suite failed!"
-
-# Copy sources to temporary directory
-PROJECT_DIR=$TMPDIR/project
-dump "Copying test program sources to: $PROJECT_DIR"
-run cp -r "$TESTAPP_DIR" "$PROJECT_DIR" &&
-run rm -rf "$PROJECT_DIR/obj" &&
-run rm -rf "$PROJECT_DIR/libs"
-fail_panic "Could not copy test program sources to: $PROJECT_DIR"
-
-# Build the test program with ndk-build.
-dump "Building test program with ndk-build"
-export NDK_MODULE_PATH="$PROGDIR"
-NDK_BUILD_FLAGS="-j$NUM_JOBS"
-if verbosity_is_higher_than 1; then
-  NDK_BUILD_FLAGS="$NDK_BUILD_FLAGS NDK_LOG=1 V=1"
-fi
-run "$NDK_DIR/ndk-build" -C "$PROJECT_DIR" $NDK_BUILD_FLAGS APP_ABI=$ABI
-fail_panic "Can't build test program!"
-
-# Unless --no-device was used, stop right here if ADB isn't in the path,
-# or there is no connected device.
-if [ "$NO_DEVICE" ]; then
-  dump "Done. Please connect a device to run all tests!"
-  clean_exit 0
-fi
-
-# Push the program to the device.
-TESTAPP=test_google_breakpad
-TESTAPP_FILE="$PROJECT_DIR/libs/$ABI/test_google_breakpad"
-if [ ! -f "$TESTAPP_FILE" ]; then
-  panic "Device requires '$ABI' binaries. None found!"
-fi
-
-# Run the program there
-dump "Installing test program on device"
-DEVICE_TMP=/data/local/tmp
-adb_push "$TESTAPP_FILE" "$DEVICE_TMP/"
-fail_panic "Cannot push test program to device!"
-
-dump "Running test program on device"
-adb_shell cd "$DEVICE_TMP" "&&" ./$TESTAPP > "$CRASH_LOG" 2>/dev/null
-if [ $? = 0 ]; then
-  panic "Test program did *not* crash as expected!"
-fi
-if verbosity_is_higher_than 0; then
-  echo -n "Crash log: "
-  cat "$CRASH_LOG"
-fi
-
-# Extract minidump from device
-MINIDUMP_NAME=$(awk '$1 == "Dump" && $2 == "path:" { print $3; }' "$CRASH_LOG")
-MINIDUMP_NAME=$(basename "$MINIDUMP_NAME")
-if [ -z "$MINIDUMP_NAME" ]; then
-  panic "Test program didn't write minidump properly!"
-fi
-
-dump "Extracting minidump: $MINIDUMP_NAME"
-adb_pull "$DEVICE_TMP/$MINIDUMP_NAME" .
-fail_panic "Can't extract minidump!"
-
-dump "Parsing test program symbols"
-if verbosity_is_higher_than 1; then
-  log "COMMAND: $TMPBIN/dump_syms \
-                $PROJECT_DIR/obj/local/$ABI/$TESTAPP >$TESTAPP.sym"
-fi
-"$TMPBIN/dump_syms" "$PROJECT_DIR/obj/local/$ABI/$TESTAPP" > $TESTAPP.sym
-fail_panic "dump_syms doesn't work!"
-
-VERSION=$(awk '$1 == "MODULE" { print $4; }' $TESTAPP.sym)
-dump "Found module version: $VERSION"
-if [ -z "$VERSION" ]; then
-  echo "ERROR: Can't find proper module version from symbol dump!"
-  head -n5 $TESTAPP.sym
-  clean_exit 1
-fi
-
-run mkdir -p "$TMPDIR/symbols/$TESTAPP/$VERSION"
-run mv $TESTAPP.sym "$TMPDIR/symbols/$TESTAPP/$VERSION/"
-
-dump "Generating stack trace"
-# Don't use 'run' to be able to send stdout and stderr to two different files.
-log "COMMAND: $TMPBIN/minidump_stackwalk $MINIDUMP_NAME symbols"
-"$TMPBIN/minidump_stackwalk" $MINIDUMP_NAME \
-                             "$TMPDIR/symbols" \
-                             > "$BUILD_LOG" 2>>"$RUN_LOG"
-fail_panic "minidump_stackwalk doesn't work!"
-
-dump "Checking stack trace content"
-
-if verbosity_is_higher_than 1; then
-  cat "$BUILD_LOG"
-fi
-
-# The generated stack trace should look like the following:
-#
-# Thread 0 (crashed)
-#  0  test_google_breakpad!crash [test_breakpad.cpp : 17 + 0x4]
-#      r4 = 0x00015530    r5 = 0xbea2cbe4    r6 = 0xffffff38    r7 = 0xbea2cb5c
-#      r8 = 0x00000000    r9 = 0x00000000   r10 = 0x00000000    fp = 0x00000000
-#      sp = 0xbea2cb50    lr = 0x00009025    pc = 0x00008f84
-#     Found by: given as instruction pointer in context
-#  1  test_google_breakpad!main [test_breakpad.cpp : 25 + 0x3]
-#      r4 = 0x00015530    r5 = 0xbea2cbe4    r6 = 0xffffff38    r7 = 0xbea2cb5c
-#      r8 = 0x00000000    r9 = 0x00000000   r10 = 0x00000000    fp = 0x00000000
-#      sp = 0xbea2cb50    pc = 0x00009025
-#     Found by: call frame info
-#  2  libc.so + 0x164e5
-#      r4 = 0x00008f64    r5 = 0xbea2cc34    r6 = 0x00000001    r7 = 0xbea2cc3c
-#      r8 = 0x00000000    r9 = 0x00000000   r10 = 0x00000000    fp = 0x00000000
-#      sp = 0xbea2cc18    pc = 0x400c34e7
-#     Found by: call frame info
-# ...
-#
-# The most important part for us is ensuring that the source location could
-# be extracted, so look at the 'test_breakpad.cpp' references here.
-#
-# First, extract all the lines with test_google_breakpad! in them, and
-# dump the corresponding crash location.
-#
-# Note that if the source location can't be extracted, the second field
-# will only be 'test_google_breakpad' without the exclamation mark.
-#
-LOCATIONS=$(awk '$2 ~ "^test_google_breakpad!.*" { print $3; }' "$BUILD_LOG")
-
-if [ -z "$LOCATIONS" ]; then
-  if verbosity_is_lower_than 1; then
-    cat "$BUILD_LOG"
-  fi
-  panic "No source location found in stack trace!"
-fi
-
-# Now check that they all match "[<source file>"
-BAD_LOCATIONS=
-for LOCATION in $LOCATIONS; do
-  case $LOCATION in
-    # Escape the opening bracket, or some shells like Dash will not
-    # match them properly.
-    \[*.cpp|\[*.cc|\[*.h) # These are valid source locations in our executable
-      ;;
-    *) # Everything else is not!
-      BAD_LOCATIONS="$BAD_LOCATIONS $LOCATION"
-      ;;
-  esac
-done
-
-if [ "$BAD_LOCATIONS" ]; then
-  dump "ERROR: Generated stack trace doesn't contain valid source locations:"
-  cat "$BUILD_LOG"
-  echo "Bad locations are: $BAD_LOCATIONS"
-  exit 1
-fi
-
-echo "All clear! Congratulations."
-
@@ -1,32 +0,0 @@
-This is a sample Android executable that can be used to test the
-Google Breakpad client library on Android.
-
-Its purpose is simply to crash and generate a minidump under /data/local/tmp.
-
-Build instructions:
-
-   cd android/sample_app
-   $NDK/ndk-build
-
-  Where $NDK points to a valid Android NDK installation.
-
-Usage instructions:
-
-   After buildind the test program, send it to a device, then run it as
-   the shell UID:
-
-     adb push libs/armeabi/test_google_breakpad /data/local/tmp
-     adb shell /data/local/tmp/test_google_breakpad
-
-   This will simply crash after dumping the name of the generated minidump
-   file.
-
-   See jni/test_breakpad.cpp for details.
-
-   Use 'armeabi-v7a' instead of 'armeabi' above to test the ARMv7-A version
-   of the binary.
-
-Note:
-   If you plan to use the library in a regular Android application, store
-   the minidump files either to your app-specific directory, or to the SDCard
-   (the latter requiring a specific permission).
@@ -1,44 +0,0 @@
-# Copyright (c) 2012, Google Inc.
-# All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions are
-# met:
-#
-#     * Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-#     * Redistributions in binary form must reproduce the above
-# copyright notice, this list of conditions and the following disclaimer
-# in the documentation and/or other materials provided with the
-# distribution.
-#     * Neither the name of Google Inc. nor the names of its
-# contributors may be used to endorse or promote products derived from
-# this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-LOCAL_PATH := $(call my-dir)
-
-include $(CLEAR_VARS)
-LOCAL_MODULE := test_google_breakpad
-LOCAL_SRC_FILES := test_breakpad.cpp
-LOCAL_STATIC_LIBRARIES += breakpad_client
-include $(BUILD_EXECUTABLE)
-
-# If NDK_MODULE_PATH is defined, import the module, otherwise do a direct
-# includes. This allows us to build in all scenarios easily.
-ifneq ($(NDK_MODULE_PATH),)
-  $(call import-module,google_breakpad)
-else
-  include $(LOCAL_PATH)/../../google_breakpad/Android.mk
-endif
@@ -1,32 +0,0 @@
-# Copyright (c) 2012, Google Inc.
-# All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions are
-# met:
-#
-#     * Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-#     * Redistributions in binary form must reproduce the above
-# copyright notice, this list of conditions and the following disclaimer
-# in the documentation and/or other materials provided with the
-# distribution.
-#     * Neither the name of Google Inc. nor the names of its
-# contributors may be used to endorse or promote products derived from
-# this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-APP_STL := stlport_static
-APP_ABI := all
-APP_CXXFLAGS := -std=c++11 -D__STDC_LIMIT_MACROS
@@ -1,57 +0,0 @@
-// Copyright (c) 2012, Google Inc.
-// All rights reserved.
-//
-// Redistribution and use in source and binary forms, with or without
-// modification, are permitted provided that the following conditions are
-// met:
-//
-//     * Redistributions of source code must retain the above copyright
-// notice, this list of conditions and the following disclaimer.
-//     * Redistributions in binary form must reproduce the above
-// copyright notice, this list of conditions and the following disclaimer
-// in the documentation and/or other materials provided with the
-// distribution.
-//     * Neither the name of Google Inc. nor the names of its
-// contributors may be used to endorse or promote products derived from
-// this software without specific prior written permission.
-//
-// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-#include <stdio.h>
-
-#include "client/linux/handler/exception_handler.h"
-#include "client/linux/handler/minidump_descriptor.h"
-
-namespace {
-
-bool DumpCallback(const google_breakpad::MinidumpDescriptor& descriptor,
-                  void* context,
-                  bool succeeded) {
-  printf("Dump path: %s\n", descriptor.path());
-  return succeeded;
-}
-
-void Crash() {
-  volatile int* a = reinterpret_cast<volatile int*>(NULL);
-  *a = 1;
-}
-
-}  // namespace
-
-int main(int argc, char* argv[]) {
-  google_breakpad::MinidumpDescriptor descriptor(".");
-  google_breakpad::ExceptionHandler eh(descriptor, NULL, DumpCallback,
-                                       NULL, true, -1);
-  Crash();
-  return 0;
-}
@@ -1,131 +0,0 @@
-#! /bin/sh
-# test-driver - basic testsuite driver script.
-
-# Slightly modified for Android, see ANDROID comment below.
-
-scriptversion=2012-06-27.10; # UTC
-
-# Copyright (C) 2011-2013 Free Software Foundation, Inc.
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program.  If not, see <http://www.gnu.org/licenses/>.
-
-# As a special exception to the GNU General Public License, if you
-# distribute this file as part of a program that contains a
-# configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-# This file is maintained in Automake, please report
-# bugs to <[email protected]> or send patches to
-# <[email protected]>.
-
-# Make unconditional expansion of undefined variables an error.  This
-# helps a lot in preventing typo-related bugs.
-set -u
-
-usage_error ()
-{
-  echo "$0: $*" >&2
-  print_usage >&2
-  exit 2
-}
-
-print_usage ()
-{
-  cat <<END
-Usage:
-  test-driver --test-name=NAME --log-file=PATH --trs-file=PATH
-              [--expect-failure={yes|no}] [--color-tests={yes|no}]
-              [--enable-hard-errors={yes|no}] [--] TEST-SCRIPT
-The '--test-name', '--log-file' and '--trs-file' options are mandatory.
-END
-}
-
-# TODO: better error handling in option parsing (in particular, ensure
-# TODO: $log_file, $trs_file and $test_name are defined).
-test_name= # Used for reporting.
-log_file=  # Where to save the output of the test script.
-trs_file=  # Where to save the metadata of the test run.
-expect_failure=no
-color_tests=no
-enable_hard_errors=yes
-while test $# -gt 0; do
-  case $1 in
-  --help) print_usage; exit $?;;
-  --version) echo "test-driver $scriptversion"; exit $?;;
-  --test-name) test_name=$2; shift;;
-  --log-file) log_file=$2; shift;;
-  --trs-file) trs_file=$2; shift;;
-  --color-tests) color_tests=$2; shift;;
-  --expect-failure) expect_failure=$2; shift;;
-  --enable-hard-errors) enable_hard_errors=$2; shift;;
-  --) shift; break;;
-  -*) usage_error "invalid option: '$1'";;
-  esac
-  shift
-done
-
-if test $color_tests = yes; then
-  # Keep this in sync with 'lib/am/check.am:$(am__tty_colors)'.
-  red='[0;31m' # Red.
-  grn='[0;32m' # Green.
-  lgn='[1;32m' # Light green.
-  blu='[1;34m' # Blue.
-  mgn='[0;35m' # Magenta.
-  std='[m'     # No color.
-else
-  red= grn= lgn= blu= mgn= std=
-fi
-
-do_exit='rm -f $log_file $trs_file; (exit $st); exit $st'
-trap "st=129; $do_exit" 1
-trap "st=130; $do_exit" 2
-trap "st=141; $do_exit" 13
-trap "st=143; $do_exit" 15
-
-# Test script is run here.
-# ANDROID: old line was: "$@" > $log_file 2>&1
-progdir=$(dirname "$0")
-"$progdir/test-shell.sh" "$@" > $log_file 2>&1
-estatus=$?
-if test $enable_hard_errors = no && test $estatus -eq 99; then
-  estatus=1
-fi
-
-case $estatus:$expect_failure in
-  0:yes) col=$red res=XPASS recheck=yes gcopy=yes;;
-  0:*)   col=$grn res=PASS  recheck=no  gcopy=no;;
-  77:*)  col=$blu res=SKIP  recheck=no  gcopy=yes;;
-  99:*)  col=$mgn res=ERROR recheck=yes gcopy=yes;;
-  *:yes) col=$lgn res=XFAIL recheck=no  gcopy=yes;;
-  *:*)   col=$red res=FAIL  recheck=yes gcopy=yes;;
-esac
-
-# Report outcome to console.
-echo "${col}${res}${std}: $test_name"
-
-# Register the test result, and other relevant metadata.
-echo ":test-result: $res" > $trs_file
-echo ":global-test-result: $res" >> $trs_file
-echo ":recheck: $recheck" >> $trs_file
-echo ":copy-in-global-log: $gcopy" >> $trs_file
-
-# Local Variables:
-# mode: shell-script
-# sh-indentation: 2
-# eval: (add-hook 'write-file-hooks 'time-stamp)
-# time-stamp-start: "scriptversion="
-# time-stamp-format: "%:y-%02m-%02d.%02H"
-# time-stamp-time-zone: "UTC"
-# time-stamp-end: "; # UTC"
-# End:
@@ -1,131 +0,0 @@
-#!/bin/sh
-#
-# Copyright (c) 2012 Google Inc.
-# All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions are
-# met:
-#
-#     * Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-#     * Redistributions in binary form must reproduce the above
-# copyright notice, this list of conditions and the following disclaimer
-# in the documentation and/or other materials provided with the
-# distribution.
-#     * Neither the name of Google Inc. nor the names of its
-# contributors may be used to endorse or promote products derived from
-# this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-# A special shell wrapper that can be used to run the Google Breakpad unit
-# tests on a connected Android device.
-#
-# This is designed to be called from the Makefile during 'make check'
-#
-
-PROGDIR=$(dirname "$0")
-PROGNAME=$(basename "$0")
-. $PROGDIR/common-functions.sh
-
-# Extract test program name first.
-TEST_PROGRAM=$1
-shift
-
-if [ -z "$TEST_PROGRAM" ]; then
-  panic "No test program/script name on the command-line!"
-fi
-
-if [ ! -f "$TEST_PROGRAM" ]; then
-  panic "Can't find test program/script: $TEST_PROGRAM"
-fi
-
-# Create test directory on the device
-TEST_DIR=/data/local/tmp/test-google-breakpad-$$
-adb_shell mkdir "$TEST_DIR" ||
-    panic "Can't create test directory on device: $TEST_DIR"
-
-# Ensure that it is always removed when the script exits.
-clean_test_dir () {
-  # Don't care about success/failure, use '$ADB shell' directly.
-  adb_shell rm -r "$TEST_DIR"
-}
-
-atexit clean_test_dir
-
-TEST_PROGRAM_NAME=$(basename "$TEST_PROGRAM")
-TEST_PROGRAM_DIR=$(dirname "$TEST_PROGRAM")
-
-# Handle special case(s) here.
-DATA_FILES=
-case $TEST_PROGRAM_NAME in
-  linux_client_unittest)
-    # linux_client_unittest will call another executable at runtime, ensure
-    # it is installed too.
-    adb_install "$TEST_PROGRAM_DIR/linux_dumper_unittest_helper" "$TEST_DIR"
-    # linux_client_unittest loads a shared library at runtime, ensure it is
-    # installed too.
-    adb_install "$TEST_PROGRAM_DIR/linux_client_unittest_shlib" "$TEST_DIR"
-    ;;
-  basic_source_line_resolver_unittest)
-    DATA_FILES="module1.out \
-                module2.out \
-                module3_bad.out \
-                module4_bad.out"
-    ;;
-  exploitability_unittest)
-    DATA_FILES="scii_read_av.dmp \
-                ascii_read_av_block_write.dmp \
-                ascii_read_av_clobber_write.dmp \
-                ascii_read_av_conditional.dmp \
-                ascii_read_av_non_null.dmp \
-                ascii_read_av_then_jmp.dmp \
-                ascii_read_av_xchg_write.dmp \
-                ascii_write_av.dmp \
-                ascii_write_av_arg_to_call.dmp \
-                exec_av_on_stack.dmp \
-                null_read_av.dmp \
-                null_write_av.dmp \
-                read_av.dmp \
-                null_read_av.dmp \
-                write_av_non_null.dmp"
-    ;;
-  fast_source_line_resolver_unittest)
-    DATA_FILES="module0.out \
-                module1.out \
-                module2.out \
-                module3_bad.out \
-                module4_bad.out"
-    ;;
-  minidump_processor_unittest|minidump_unittest)
-    DATA_FILES="src/processor/testdata/minidump2.dmp"
-    ;;
-esac
-
-# Install the data files, their path is relative to the environment
-# variable 'srcdir'
-for FILE in $DATA_FILES; do
-  FILEDIR=src/processor/testdata/$(dirname "$FILE")
-  adb_shell mkdir -p "$TEST_DIR/$FILEDIR"
-  adb_install "${srcdir:-.}/$FILE" "$TEST_DIR"/"$FILE"
-done
-
-# Copy test program to device
-adb_install "$TEST_PROGRAM" "$TEST_DIR"
-
-# Run it
-adb_shell "cd $TEST_DIR && LD_LIBRARY_PATH=. ./$TEST_PROGRAM_NAME $@"
-
-# Note: exiting here will call cleanup_exit which will remove the temporary
-#       files from the device.
@@ -1,42 +0,0 @@
-version: '{build}'
-
-environment:
-  GYP_MSVS_VERSION: 2013
-
-platform:
-  - Win32
-
-configuration:
-  - Debug
-  - Release
-
-# Use the source dir expected by gclient.
-clone_folder: c:\projects\breakpad\src
-
-# Before checkout.
-init:
-  - cd %APPVEYOR_BUILD_FOLDER%\..\..
-  - appveyor DownloadFile https://storage.googleapis.com/chrome-infra/depot_tools.zip
-  - 7z -bd x depot_tools.zip -odepot_tools
-  - depot_tools\update_depot_tools
-  - cd %APPVEYOR_BUILD_FOLDER%
-
-# After checkout.
-install:
-  - PATH C:\projects\depot_tools;%PATH%
-  - cd %APPVEYOR_BUILD_FOLDER%\..
-  - gclient config https://%APPVEYOR_REPO_PROVIDER%.com/%APPVEYOR_REPO_NAME% --unmanaged --name=src
-  - gclient sync
-
-build_script:
-  - cd %APPVEYOR_BUILD_FOLDER%
-  - msbuild src\client\windows\breakpad_client.sln /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll" /m /verbosity:normal
-  - msbuild src\tools\windows\tools_windows.sln    /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll" /m /verbosity:normal
-
-test_script:
-  - src\client\windows\%CONFIGURATION%\client_tests.exe
-  - src\tools\windows\%CONFIGURATION%\dump_syms_unittest.exe
-
-artifacts:
-  - path: '**\*.exe'
-  - path: '**\*.lib'
@@ -1,270 +0,0 @@
-#! /bin/sh
-# Wrapper for Microsoft lib.exe
-
-me=ar-lib
-scriptversion=2012-03-01.08; # UTC
-
-# Copyright (C) 2010-2014 Free Software Foundation, Inc.
-# Written by Peter Rosin <[email protected]>.
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program.  If not, see <http://www.gnu.org/licenses/>.
-
-# As a special exception to the GNU General Public License, if you
-# distribute this file as part of a program that contains a
-# configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-# This file is maintained in Automake, please report
-# bugs to <[email protected]> or send patches to
-# <[email protected]>.
-
-
-# func_error message
-func_error ()
-{
-  echo "$me: $1" 1>&2
-  exit 1
-}
-
-file_conv=
-
-# func_file_conv build_file
-# Convert a $build file to $host form and store it in $file
-# Currently only supports Windows hosts.
-func_file_conv ()
-{
-  file=$1
-  case $file in
-    / | /[!/]*) # absolute file, and not a UNC file
-      if test -z "$file_conv"; then
-	# lazily determine how to convert abs files
-	case `uname -s` in
-	  MINGW*)
-	    file_conv=mingw
-	    ;;
-	  CYGWIN*)
-	    file_conv=cygwin
-	    ;;
-	  *)
-	    file_conv=wine
-	    ;;
-	esac
-      fi
-      case $file_conv in
-	mingw)
-	  file=`cmd //C echo "$file " | sed -e 's/"\(.*\) " *$/\1/'`
-	  ;;
-	cygwin)
-	  file=`cygpath -m "$file" || echo "$file"`
-	  ;;
-	wine)
-	  file=`winepath -w "$file" || echo "$file"`
-	  ;;
-      esac
-      ;;
-  esac
-}
-
-# func_at_file at_file operation archive
-# Iterate over all members in AT_FILE performing OPERATION on ARCHIVE
-# for each of them.
-# When interpreting the content of the @FILE, do NOT use func_file_conv,
-# since the user would need to supply preconverted file names to
-# binutils ar, at least for MinGW.
-func_at_file ()
-{
-  operation=$2
-  archive=$3
-  at_file_contents=`cat "$1"`
-  eval set x "$at_file_contents"
-  shift
-
-  for member
-  do
-    $AR -NOLOGO $operation:"$member" "$archive" || exit $?
-  done
-}
-
-case $1 in
-  '')
-     func_error "no command.  Try '$0 --help' for more information."
-     ;;
-  -h | --h*)
-    cat <<EOF
-Usage: $me [--help] [--version] PROGRAM ACTION ARCHIVE [MEMBER...]
-
-Members may be specified in a file named with @FILE.
-EOF
-    exit $?
-    ;;
-  -v | --v*)
-    echo "$me, version $scriptversion"
-    exit $?
-    ;;
-esac
-
-if test $# -lt 3; then
-  func_error "you must specify a program, an action and an archive"
-fi
-
-AR=$1
-shift
-while :
-do
-  if test $# -lt 2; then
-    func_error "you must specify a program, an action and an archive"
-  fi
-  case $1 in
-    -lib | -LIB \
-    | -ltcg | -LTCG \
-    | -machine* | -MACHINE* \
-    | -subsystem* | -SUBSYSTEM* \
-    | -verbose | -VERBOSE \
-    | -wx* | -WX* )
-      AR="$AR $1"
-      shift
-      ;;
-    *)
-      action=$1
-      shift
-      break
-      ;;
-  esac
-done
-orig_archive=$1
-shift
-func_file_conv "$orig_archive"
-archive=$file
-
-# strip leading dash in $action
-action=${action#-}
-
-delete=
-extract=
-list=
-quick=
-replace=
-index=
-create=
-
-while test -n "$action"
-do
-  case $action in
-    d*) delete=yes  ;;
-    x*) extract=yes ;;
-    t*) list=yes    ;;
-    q*) quick=yes   ;;
-    r*) replace=yes ;;
-    s*) index=yes   ;;
-    S*)             ;; # the index is always updated implicitly
-    c*) create=yes  ;;
-    u*)             ;; # TODO: don't ignore the update modifier
-    v*)             ;; # TODO: don't ignore the verbose modifier
-    *)
-      func_error "unknown action specified"
-      ;;
-  esac
-  action=${action#?}
-done
-
-case $delete$extract$list$quick$replace,$index in
-  yes,* | ,yes)
-    ;;
-  yesyes*)
-    func_error "more than one action specified"
-    ;;
-  *)
-    func_error "no action specified"
-    ;;
-esac
-
-if test -n "$delete"; then
-  if test ! -f "$orig_archive"; then
-    func_error "archive not found"
-  fi
-  for member
-  do
-    case $1 in
-      @*)
-        func_at_file "${1#@}" -REMOVE "$archive"
-        ;;
-      *)
-        func_file_conv "$1"
-        $AR -NOLOGO -REMOVE:"$file" "$archive" || exit $?
-        ;;
-    esac
-  done
-
-elif test -n "$extract"; then
-  if test ! -f "$orig_archive"; then
-    func_error "archive not found"
-  fi
-  if test $# -gt 0; then
-    for member
-    do
-      case $1 in
-        @*)
-          func_at_file "${1#@}" -EXTRACT "$archive"
-          ;;
-        *)
-          func_file_conv "$1"
-          $AR -NOLOGO -EXTRACT:"$file" "$archive" || exit $?
-          ;;
-      esac
-    done
-  else
-    $AR -NOLOGO -LIST "$archive" | sed -e 's/\\/\\\\/g' | while read member
-    do
-      $AR -NOLOGO -EXTRACT:"$member" "$archive" || exit $?
-    done
-  fi
-
-elif test -n "$quick$replace"; then
-  if test ! -f "$orig_archive"; then
-    if test -z "$create"; then
-      echo "$me: creating $orig_archive"
-    fi
-    orig_archive=
-  else
-    orig_archive=$archive
-  fi
-
-  for member
-  do
-    case $1 in
-    @*)
-      func_file_conv "${1#@}"
-      set x "$@" "@$file"
-      ;;
-    *)
-      func_file_conv "$1"
-      set x "$@" "$file"
-      ;;
-    esac
-    shift
-    shift
-  done
-
-  if test -n "$orig_archive"; then
-    $AR -NOLOGO -OUT:"$archive" "$orig_archive" "$@" || exit $?
-  else
-    $AR -NOLOGO -OUT:"$archive" "$@" || exit $?
-  fi
-
-elif test -n "$list"; then
-  if test ! -f "$orig_archive"; then
-    func_error "archive not found"
-  fi
-  $AR -NOLOGO -LIST "$archive" || exit $?
-fi
@@ -1,347 +0,0 @@
-#! /bin/sh
-# Wrapper for compilers which do not understand '-c -o'.
-
-scriptversion=2012-10-14.11; # UTC
-
-# Copyright (C) 1999-2014 Free Software Foundation, Inc.
-# Written by Tom Tromey <[email protected]>.
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program.  If not, see <http://www.gnu.org/licenses/>.
-
-# As a special exception to the GNU General Public License, if you
-# distribute this file as part of a program that contains a
-# configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-# This file is maintained in Automake, please report
-# bugs to <[email protected]> or send patches to
-# <[email protected]>.
-
-nl='
-'
-
-# We need space, tab and new line, in precisely that order.  Quoting is
-# there to prevent tools from complaining about whitespace usage.
-IFS=" ""	$nl"
-
-file_conv=
-
-# func_file_conv build_file lazy
-# Convert a $build file to $host form and store it in $file
-# Currently only supports Windows hosts. If the determined conversion
-# type is listed in (the comma separated) LAZY, no conversion will
-# take place.
-func_file_conv ()
-{
-  file=$1
-  case $file in
-    / | /[!/]*) # absolute file, and not a UNC file
-      if test -z "$file_conv"; then
-	# lazily determine how to convert abs files
-	case `uname -s` in
-	  MINGW*)
-	    file_conv=mingw
-	    ;;
-	  CYGWIN*)
-	    file_conv=cygwin
-	    ;;
-	  *)
-	    file_conv=wine
-	    ;;
-	esac
-      fi
-      case $file_conv/,$2, in
-	*,$file_conv,*)
-	  ;;
-	mingw/*)
-	  file=`cmd //C echo "$file " | sed -e 's/"\(.*\) " *$/\1/'`
-	  ;;
-	cygwin/*)
-	  file=`cygpath -m "$file" || echo "$file"`
-	  ;;
-	wine/*)
-	  file=`winepath -w "$file" || echo "$file"`
-	  ;;
-      esac
-      ;;
-  esac
-}
-
-# func_cl_dashL linkdir
-# Make cl look for libraries in LINKDIR
-func_cl_dashL ()
-{
-  func_file_conv "$1"
-  if test -z "$lib_path"; then
-    lib_path=$file
-  else
-    lib_path="$lib_path;$file"
-  fi
-  linker_opts="$linker_opts -LIBPATH:$file"
-}
-
-# func_cl_dashl library
-# Do a library search-path lookup for cl
-func_cl_dashl ()
-{
-  lib=$1
-  found=no
-  save_IFS=$IFS
-  IFS=';'
-  for dir in $lib_path $LIB
-  do
-    IFS=$save_IFS
-    if $shared && test -f "$dir/$lib.dll.lib"; then
-      found=yes
-      lib=$dir/$lib.dll.lib
-      break
-    fi
-    if test -f "$dir/$lib.lib"; then
-      found=yes
-      lib=$dir/$lib.lib
-      break
-    fi
-    if test -f "$dir/lib$lib.a"; then
-      found=yes
-      lib=$dir/lib$lib.a
-      break
-    fi
-  done
-  IFS=$save_IFS
-
-  if test "$found" != yes; then
-    lib=$lib.lib
-  fi
-}
-
-# func_cl_wrapper cl arg...
-# Adjust compile command to suit cl
-func_cl_wrapper ()
-{
-  # Assume a capable shell
-  lib_path=
-  shared=:
-  linker_opts=
-  for arg
-  do
-    if test -n "$eat"; then
-      eat=
-    else
-      case $1 in
-	-o)
-	  # configure might choose to run compile as 'compile cc -o foo foo.c'.
-	  eat=1
-	  case $2 in
-	    *.o | *.[oO][bB][jJ])
-	      func_file_conv "$2"
-	      set x "$@" -Fo"$file"
-	      shift
-	      ;;
-	    *)
-	      func_file_conv "$2"
-	      set x "$@" -Fe"$file"
-	      shift
-	      ;;
-	  esac
-	  ;;
-	-I)
-	  eat=1
-	  func_file_conv "$2" mingw
-	  set x "$@" -I"$file"
-	  shift
-	  ;;
-	-I*)
-	  func_file_conv "${1#-I}" mingw
-	  set x "$@" -I"$file"
-	  shift
-	  ;;
-	-l)
-	  eat=1
-	  func_cl_dashl "$2"
-	  set x "$@" "$lib"
-	  shift
-	  ;;
-	-l*)
-	  func_cl_dashl "${1#-l}"
-	  set x "$@" "$lib"
-	  shift
-	  ;;
-	-L)
-	  eat=1
-	  func_cl_dashL "$2"
-	  ;;
-	-L*)
-	  func_cl_dashL "${1#-L}"
-	  ;;
-	-static)
-	  shared=false
-	  ;;
-	-Wl,*)
-	  arg=${1#-Wl,}
-	  save_ifs="$IFS"; IFS=','
-	  for flag in $arg; do
-	    IFS="$save_ifs"
-	    linker_opts="$linker_opts $flag"
-	  done
-	  IFS="$save_ifs"
-	  ;;
-	-Xlinker)
-	  eat=1
-	  linker_opts="$linker_opts $2"
-	  ;;
-	-*)
-	  set x "$@" "$1"
-	  shift
-	  ;;
-	*.cc | *.CC | *.cxx | *.CXX | *.[cC]++)
-	  func_file_conv "$1"
-	  set x "$@" -Tp"$file"
-	  shift
-	  ;;
-	*.c | *.cpp | *.CPP | *.lib | *.LIB | *.Lib | *.OBJ | *.obj | *.[oO])
-	  func_file_conv "$1" mingw
-	  set x "$@" "$file"
-	  shift
-	  ;;
-	*)
-	  set x "$@" "$1"
-	  shift
-	  ;;
-      esac
-    fi
-    shift
-  done
-  if test -n "$linker_opts"; then
-    linker_opts="-link$linker_opts"
-  fi
-  exec "$@" $linker_opts
-  exit 1
-}
-
-eat=
-
-case $1 in
-  '')
-     echo "$0: No command.  Try '$0 --help' for more information." 1>&2
-     exit 1;
-     ;;
-  -h | --h*)
-    cat <<\EOF
-Usage: compile [--help] [--version] PROGRAM [ARGS]
-
-Wrapper for compilers which do not understand '-c -o'.
-Remove '-o dest.o' from ARGS, run PROGRAM with the remaining
-arguments, and rename the output as expected.
-
-If you are trying to build a whole package this is not the
-right script to run: please start by reading the file 'INSTALL'.
-
-Report bugs to <[email protected]>.
-EOF
-    exit $?
-    ;;
-  -v | --v*)
-    echo "compile $scriptversion"
-    exit $?
-    ;;
-  cl | *[/\\]cl | cl.exe | *[/\\]cl.exe )
-    func_cl_wrapper "$@"      # Doesn't return...
-    ;;
-esac
-
-ofile=
-cfile=
-
-for arg
-do
-  if test -n "$eat"; then
-    eat=
-  else
-    case $1 in
-      -o)
-	# configure might choose to run compile as 'compile cc -o foo foo.c'.
-	# So we strip '-o arg' only if arg is an object.
-	eat=1
-	case $2 in
-	  *.o | *.obj)
-	    ofile=$2
-	    ;;
-	  *)
-	    set x "$@" -o "$2"
-	    shift
-	    ;;
-	esac
-	;;
-      *.c)
-	cfile=$1
-	set x "$@" "$1"
-	shift
-	;;
-      *)
-	set x "$@" "$1"
-	shift
-	;;
-    esac
-  fi
-  shift
-done
-
-if test -z "$ofile" || test -z "$cfile"; then
-  # If no '-o' option was seen then we might have been invoked from a
-  # pattern rule where we don't need one.  That is ok -- this is a
-  # normal compilation that the losing compiler can handle.  If no
-  # '.c' file was seen then we are probably linking.  That is also
-  # ok.
-  exec "$@"
-fi
-
-# Name of file we expect compiler to create.
-cofile=`echo "$cfile" | sed 's|^.*[\\/]||; s|^[a-zA-Z]:||; s/\.c$/.o/'`
-
-# Create the lock directory.
-# Note: use '[/\\:.-]' here to ensure that we don't use the same name
-# that we are using for the .o file.  Also, base the name on the expected
-# object file name, since that is what matters with a parallel build.
-lockdir=`echo "$cofile" | sed -e 's|[/\\:.-]|_|g'`.d
-while true; do
-  if mkdir "$lockdir" >/dev/null 2>&1; then
-    break
-  fi
-  sleep 1
-done
-# FIXME: race condition here if user kills between mkdir and trap.
-trap "rmdir '$lockdir'; exit 1" 1 2 15
-
-# Run the compile.
-"$@"
-ret=$?
-
-if test -f "$cofile"; then
-  test "$cofile" = "$ofile" || mv "$cofile" "$ofile"
-elif test -f "${cofile}bj"; then
-  test "${cofile}bj" = "$ofile" || mv "${cofile}bj" "$ofile"
-fi
-
-rmdir "$lockdir"
-exit $ret
-
-# Local Variables:
-# mode: shell-script
-# sh-indentation: 2
-# eval: (add-hook 'write-file-hooks 'time-stamp)
-# time-stamp-start: "scriptversion="
-# time-stamp-format: "%:y-%02m-%02d.%02H"
-# time-stamp-time-zone: "UTC"
-# time-stamp-end: "; # UTC"
-# End:
@@ -1,791 +0,0 @@
-#! /bin/sh
-# depcomp - compile a program generating dependencies as side-effects
-
-scriptversion=2013-05-30.07; # UTC
-
-# Copyright (C) 1999-2014 Free Software Foundation, Inc.
-
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
-
-# You should have received a copy of the GNU General Public License
-# along with this program.  If not, see <http://www.gnu.org/licenses/>.
-
-# As a special exception to the GNU General Public License, if you
-# distribute this file as part of a program that contains a
-# configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-# Originally written by Alexandre Oliva <[email protected]>.
-
-case $1 in
-  '')
-    echo "$0: No command.  Try '$0 --help' for more information." 1>&2
-    exit 1;
-    ;;
-  -h | --h*)
-    cat <<\EOF
-Usage: depcomp [--help] [--version] PROGRAM [ARGS]
-
-Run PROGRAMS ARGS to compile a file, generating dependencies
-as side-effects.
-
-Environment variables:
-  depmode     Dependency tracking mode.
-  source      Source file read by 'PROGRAMS ARGS'.
-  object      Object file output by 'PROGRAMS ARGS'.
-  DEPDIR      directory where to store dependencies.
-  depfile     Dependency file to output.
-  tmpdepfile  Temporary file to use when outputting dependencies.
-  libtool     Whether libtool is used (yes/no).
-
-Report bugs to <[email protected]>.
-EOF
-    exit $?
-    ;;
-  -v | --v*)
-    echo "depcomp $scriptversion"
-    exit $?
-    ;;
-esac
-
-# Get the directory component of the given path, and save it in the
-# global variables '$dir'.  Note that this directory component will
-# be either empty or ending with a '/' character.  This is deliberate.
-set_dir_from ()
-{
-  case $1 in
-    */*) dir=`echo "$1" | sed -e 's|/[^/]*$|/|'`;;
-      *) dir=;;
-  esac
-}
-
-# Get the suffix-stripped basename of the given path, and save it the
-# global variable '$base'.
-set_base_from ()
-{
-  base=`echo "$1" | sed -e 's|^.*/||' -e 's/\.[^.]*$//'`
-}
-
-# If no dependency file was actually created by the compiler invocation,
-# we still have to create a dummy depfile, to avoid errors with the
-# Makefile "include basename.Plo" scheme.
-make_dummy_depfile ()
-{
-  echo "#dummy" > "$depfile"
-}
-
-# Factor out some common post-processing of the generated depfile.
-# Requires the auxiliary global variable '$tmpdepfile' to be set.
-aix_post_process_depfile ()
-{
-  # If the compiler actually managed to produce a dependency file,
-  # post-process it.
-  if test -f "$tmpdepfile"; then
-    # Each line is of the form 'foo.o: dependency.h'.
-    # Do two passes, one to just change these to
-    #   $object: dependency.h
-    # and one to simply output
-    #   dependency.h:
-    # which is needed to avoid the deleted-header problem.
-    { sed -e "s,^.*\.[$lower]*:,$object:," < "$tmpdepfile"
-      sed -e "s,^.*\.[$lower]*:[$tab ]*,," -e 's,$,:,' < "$tmpdepfile"
-    } > "$depfile"
-    rm -f "$tmpdepfile"
-  else
-    make_dummy_depfile
-  fi
-}
-
-# A tabulation character.
-tab='	'
-# A newline character.
-nl='
-'
-# Character ranges might be problematic outside the C locale.
-# These definitions help.
-upper=ABCDEFGHIJKLMNOPQRSTUVWXYZ
-lower=abcdefghijklmnopqrstuvwxyz
-digits=0123456789
-alpha=${upper}${lower}
-
-if test -z "$depmode" || test -z "$source" || test -z "$object"; then
-  echo "depcomp: Variables source, object and depmode must be set" 1>&2
-  exit 1
-fi
-
-# Dependencies for sub/bar.o or sub/bar.obj go into sub/.deps/bar.Po.
-depfile=${depfile-`echo "$object" |
-  sed 's|[^\\/]*$|'${DEPDIR-.deps}'/&|;s|\.\([^.]*\)$|.P\1|;s|Pobj$|Po|'`}
-tmpdepfile=${tmpdepfile-`echo "$depfile" | sed 's/\.\([^.]*\)$/.T\1/'`}
-
-rm -f "$tmpdepfile"
-
-# Avoid interferences from the environment.
-gccflag= dashmflag=
-
-# Some modes work just like other modes, but use different flags.  We
-# parameterize here, but still list the modes in the big case below,
-# to make depend.m4 easier to write.  Note that we *cannot* use a case
-# here, because this file can only contain one case statement.
-if test "$depmode" = hp; then
-  # HP compiler uses -M and no extra arg.
-  gccflag=-M
-  depmode=gcc
-fi
-
-if test "$depmode" = dashXmstdout; then
-  # This is just like dashmstdout with a different argument.
-  dashmflag=-xM
-  depmode=dashmstdout
-fi
-
-cygpath_u="cygpath -u -f -"
-if test "$depmode" = msvcmsys; then
-  # This is just like msvisualcpp but w/o cygpath translation.
-  # Just convert the backslash-escaped backslashes to single forward
-  # slashes to satisfy depend.m4
-  cygpath_u='sed s,\\\\,/,g'
-  depmode=msvisualcpp
-fi
-
-if test "$depmode" = msvc7msys; then
-  # This is just like msvc7 but w/o cygpath translation.
-  # Just convert the backslash-escaped backslashes to single forward
-  # slashes to satisfy depend.m4
-  cygpath_u='sed s,\\\\,/,g'
-  depmode=msvc7
-fi
-
-if test "$depmode" = xlc; then
-  # IBM C/C++ Compilers xlc/xlC can output gcc-like dependency information.
-  gccflag=-qmakedep=gcc,-MF
-  depmode=gcc
-fi
-
-case "$depmode" in
-gcc3)
-## gcc 3 implements dependency tracking that does exactly what
-## we want.  Yay!  Note: for some reason libtool 1.4 doesn't like
-## it if -MD -MP comes after the -MF stuff.  Hmm.
-## Unfortunately, FreeBSD c89 acceptance of flags depends upon
-## the command line argument order; so add the flags where they
-## appear in depend2.am.  Note that the slowdown incurred here
-## affects only configure: in makefiles, %FASTDEP% shortcuts this.
-  for arg
-  do
-    case $arg in
-    -c) set fnord "$@" -MT "$object" -MD -MP -MF "$tmpdepfile" "$arg" ;;
-    *)  set fnord "$@" "$arg" ;;
-    esac
-    shift # fnord
-    shift # $arg
-  done
-  "$@"
-  stat=$?
-  if test $stat -ne 0; then
-    rm -f "$tmpdepfile"
-    exit $stat
-  fi
-  mv "$tmpdepfile" "$depfile"
-  ;;
-
-gcc)
-## Note that this doesn't just cater to obsosete pre-3.x GCC compilers.
-## but also to in-use compilers like IMB xlc/xlC and the HP C compiler.
-## (see the conditional assignment to $gccflag above).
-## There are various ways to get dependency output from gcc.  Here's
-## why we pick this rather obscure method:
-## - Don't want to use -MD because we'd like the dependencies to end
-##   up in a subdir.  Having to rename by hand is ugly.
-##   (We might end up doing this anyway to support other compilers.)
-## - The DEPENDENCIES_OUTPUT environment variable makes gcc act like
-##   -MM, not -M (despite what the docs say).  Also, it might not be
-##   supported by the other compilers which use the 'gcc' depmode.
-## - Using -M directly means running the compiler twice (even worse
-##   than renaming).
-  if test -z "$gccflag"; then
-    gccflag=-MD,
-  fi
-  "$@" -Wp,"$gccflag$tmpdepfile"
-  stat=$?
-  if test $stat -ne 0; then
-    rm -f "$tmpdepfile"
-    exit $stat
-  fi
-  rm -f "$depfile"
-  echo "$object : \\" > "$depfile"
-  # The second -e expression handles DOS-style file names with drive
-  # letters.
-  sed -e 's/^[^:]*: / /' \
-      -e 's/^['$alpha']:\/[^:]*: / /' < "$tmpdepfile" >> "$depfile"
-## This next piece of magic avoids the "deleted header file" problem.
-## The problem is that when a header file which appears in a .P file
-## is deleted, the dependency causes make to die (because there is
-## typically no way to rebuild the header).  We avoid this by adding
-## dummy dependencies for each header file.  Too bad gcc doesn't do
-## this for us directly.
-## Some versions of gcc put a space before the ':'.  On the theory
-## that the space means something, we add a space to the output as
-## well.  hp depmode also adds that space, but also prefixes the VPATH
-## to the object.  Take care to not repeat it in the output.
-## Some versions of the HPUX 10.20 sed can't process this invocation
-## correctly.  Breaking it into two sed invocations is a workaround.
-  tr ' ' "$nl" < "$tmpdepfile" \
-    | sed -e 's/^\\$//' -e '/^$/d' -e "s|.*$object$||" -e '/:$/d' \
-    | sed -e 's/$/ :/' >> "$depfile"
-  rm -f "$tmpdepfile"
-  ;;
-
-hp)
-  # This case exists only to let depend.m4 do its work.  It works by
-  # looking at the text of this script.  This case will never be run,
-  # since it is checked for above.
-  exit 1
-  ;;
-
-sgi)
-  if test "$libtool" = yes; then
-    "$@" "-Wp,-MDupdate,$tmpdepfile"
-  else
-    "$@" -MDupdate "$tmpdepfile"
-  fi
-  stat=$?
-  if test $stat -ne 0; then
-    rm -f "$tmpdepfile"
-    exit $stat
-  fi
-  rm -f "$depfile"
-
-  if test -f "$tmpdepfile"; then  # yes, the sourcefile depend on other files
-    echo "$object : \\" > "$depfile"
-    # Clip off the initial element (the dependent).  Don't try to be
-    # clever and replace this with sed code, as IRIX sed won't handle
-    # lines with more than a fixed number of characters (4096 in
-    # IRIX 6.2 sed, 8192 in IRIX 6.5).  We also remove comment lines;
-    # the IRIX cc adds comments like '#:fec' to the end of the
-    # dependency line.
-    tr ' ' "$nl" < "$tmpdepfile" \
-      | sed -e 's/^.*\.o://' -e 's/#.*$//' -e '/^$/ d' \
-      | tr "$nl" ' ' >> "$depfile"
-    echo >> "$depfile"
-    # The second pass generates a dummy entry for each header file.
-    tr ' ' "$nl" < "$tmpdepfile" \
-      | sed -e 's/^.*\.o://' -e 's/#.*$//' -e '/^$/ d' -e 's/$/:/' \
-      >> "$depfile"
-  else
-    make_dummy_depfile
-  fi
-  rm -f "$tmpdepfile"
-  ;;
-
-xlc)
-  # This case exists only to let depend.m4 do its work.  It works by
-  # looking at the text of this script.  This case will never be run,
-  # since it is checked for above.
-  exit 1
-  ;;
-
-aix)
-  # The C for AIX Compiler uses -M and outputs the dependencies
-  # in a .u file.  In older versions, this file always lives in the
-  # current directory.  Also, the AIX compiler puts '$object:' at the
-  # start of each line; $object doesn't have directory information.
-  # Version 6 uses the directory in both cases.
-  set_dir_from "$object"
-  set_base_from "$object"
-  if test "$libtool" = yes; then
-    tmpdepfile1=$dir$base.u
-    tmpdepfile2=$base.u
-    tmpdepfile3=$dir.libs/$base.u
-    "$@" -Wc,-M
-  else
-    tmpdepfile1=$dir$base.u
-    tmpdepfile2=$dir$base.u
-    tmpdepfile3=$dir$base.u
-    "$@" -M
-  fi
-  stat=$?
-  if test $stat -ne 0; then
-    rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3"
-    exit $stat
-  fi
-
-  for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3"
-  do
-    test -f "$tmpdepfile" && break
-  done
-  aix_post_process_depfile
-  ;;
-
-tcc)
-  # tcc (Tiny C Compiler) understand '-MD -MF file' since version 0.9.26
-  # FIXME: That version still under development at the moment of writing.
-  #        Make that this statement remains true also for stable, released
-  #        versions.
-  # It will wrap lines (doesn't matter whether long or short) with a
-  # trailing '\', as in:
-  #
-  #   foo.o : \
-  #    foo.c \
-  #    foo.h \
-  #
-  # It will put a trailing '\' even on the last line, and will use leading
-  # spaces rather than leading tabs (at least since its commit 0394caf7
-  # "Emit spaces for -MD").
-  "$@" -MD -MF "$tmpdepfile"
-  stat=$?
-  if test $stat -ne 0; then
-    rm -f "$tmpdepfile"
-    exit $stat
-  fi
-  rm -f "$depfile"
-  # Each non-empty line is of the form 'foo.o : \' or ' dep.h \'.
-  # We have to change lines of the first kind to '$object: \'.
-  sed -e "s|.*:|$object :|" < "$tmpdepfile" > "$depfile"
-  # And for each line of the second kind, we have to emit a 'dep.h:'
-  # dummy dependency, to avoid the deleted-header problem.
-  sed -n -e 's|^  *\(.*\) *\\$|\1:|p' < "$tmpdepfile" >> "$depfile"
-  rm -f "$tmpdepfile"
-  ;;
-
-## The order of this option in the case statement is important, since the
-## shell code in configure will try each of these formats in the order
-## listed in this file.  A plain '-MD' option would be understood by many
-## compilers, so we must ensure this comes after the gcc and icc options.
-pgcc)
-  # Portland's C compiler understands '-MD'.
-  # Will always output deps to 'file.d' where file is the root name of the
-  # source file under compilation, even if file resides in a subdirectory.
-  # The object file name does not affect the name of the '.d' file.
-  # pgcc 10.2 will output
-  #    foo.o: sub/foo.c sub/foo.h
-  # and will wrap long lines using '\' :
-  #    foo.o: sub/foo.c ... \
-  #     sub/foo.h ... \
-  #     ...
-  set_dir_from "$object"
-  # Use the source, not the object, to determine the base name, since
-  # that's sadly what pgcc will do too.
-  set_base_from "$source"
-  tmpdepfile=$base.d
-
-  # For projects that build the same source file twice into different object
-  # files, the pgcc approach of using the *source* file root name can cause
-  # problems in parallel builds.  Use a locking strategy to avoid stomping on
-  # the same $tmpdepfile.
-  lockdir=$base.d-lock
-  trap "
-    echo '$0: caught signal, cleaning up...' >&2
-    rmdir '$lockdir'
-    exit 1
-  " 1 2 13 15
-  numtries=100
-  i=$numtries
-  while test $i -gt 0; do
-    # mkdir is a portable test-and-set.
-    if mkdir "$lockdir" 2>/dev/null; then
-      # This process acquired the lock.
-      "$@" -MD
-      stat=$?
-      # Release the lock.
-      rmdir "$lockdir"
-      break
-    else
-      # If the lock is being held by a different process, wait
-      # until the winning process is done or we timeout.
-      while test -d "$lockdir" && test $i -gt 0; do
-        sleep 1
-        i=`expr $i - 1`
-      done
-    fi
-    i=`expr $i - 1`
-  done
-  trap - 1 2 13 15
-  if test $i -le 0; then
-    echo "$0: failed to acquire lock after $numtries attempts" >&2
-    echo "$0: check lockdir '$lockdir'" >&2
-    exit 1
-  fi
-
-  if test $stat -ne 0; then
-    rm -f "$tmpdepfile"
-    exit $stat
-  fi
-  rm -f "$depfile"
-  # Each line is of the form `foo.o: dependent.h',
-  # or `foo.o: dep1.h dep2.h \', or ` dep3.h dep4.h \'.
-  # Do two passes, one to just change these to
-  # `$object: dependent.h' and one to simply `dependent.h:'.
-  sed "s,^[^:]*:,$object :," < "$tmpdepfile" > "$depfile"
-  # Some versions of the HPUX 10.20 sed can't process this invocation
-  # correctly.  Breaking it into two sed invocations is a workaround.
-  sed 's,^[^:]*: \(.*\)$,\1,;s/^\\$//;/^$/d;/:$/d' < "$tmpdepfile" \
-    | sed -e 's/$/ :/' >> "$depfile"
-  rm -f "$tmpdepfile"
-  ;;
-
-hp2)
-  # The "hp" stanza above does not work with aCC (C++) and HP's ia64
-  # compilers, which have integrated preprocessors.  The correct option
-  # to use with these is +Maked; it writes dependencies to a file named
-  # 'foo.d', which lands next to the object file, wherever that
-  # happens to be.
-  # Much of this is similar to the tru64 case; see comments there.
-  set_dir_from  "$object"
-  set_base_from "$object"
-  if test "$libtool" = yes; then
-    tmpdepfile1=$dir$base.d
-    tmpdepfile2=$dir.libs/$base.d
-    "$@" -Wc,+Maked
-  else
-    tmpdepfile1=$dir$base.d
-    tmpdepfile2=$dir$base.d
-    "$@" +Maked
-  fi
-  stat=$?
-  if test $stat -ne 0; then
-     rm -f "$tmpdepfile1" "$tmpdepfile2"
-     exit $stat
-  fi
-
-  for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2"
-  do
-    test -f "$tmpdepfile" && break
-  done
-  if test -f "$tmpdepfile"; then
-    sed -e "s,^.*\.[$lower]*:,$object:," "$tmpdepfile" > "$depfile"
-    # Add 'dependent.h:' lines.
-    sed -ne '2,${
-               s/^ *//
-               s/ \\*$//
-               s/$/:/
-               p
-             }' "$tmpdepfile" >> "$depfile"
-  else
-    make_dummy_depfile
-  fi
-  rm -f "$tmpdepfile" "$tmpdepfile2"
-  ;;
-
-tru64)
-  # The Tru64 compiler uses -MD to generate dependencies as a side
-  # effect.  'cc -MD -o foo.o ...' puts the dependencies into 'foo.o.d'.
-  # At least on Alpha/Redhat 6.1, Compaq CCC V6.2-504 seems to put
-  # dependencies in 'foo.d' instead, so we check for that too.
-  # Subdirectories are respected.
-  set_dir_from  "$object"
-  set_base_from "$object"
-
-  if test "$libtool" = yes; then
-    # Libtool generates 2 separate objects for the 2 libraries.  These
-    # two compilations output dependencies in $dir.libs/$base.o.d and
-    # in $dir$base.o.d.  We have to check for both files, because
-    # one of the two compilations can be disabled.  We should prefer
-    # $dir$base.o.d over $dir.libs/$base.o.d because the latter is
-    # automatically cleaned when .libs/ is deleted, while ignoring
-    # the former would cause a distcleancheck panic.
-    tmpdepfile1=$dir$base.o.d          # libtool 1.5
-    tmpdepfile2=$dir.libs/$base.o.d    # Likewise.
-    tmpdepfile3=$dir.libs/$base.d      # Compaq CCC V6.2-504
-    "$@" -Wc,-MD
-  else
-    tmpdepfile1=$dir$base.d
-    tmpdepfile2=$dir$base.d
-    tmpdepfile3=$dir$base.d
-    "$@" -MD
-  fi
-
-  stat=$?
-  if test $stat -ne 0; then
-    rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3"
-    exit $stat
-  fi
-
-  for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3"
-  do
-    test -f "$tmpdepfile" && break
-  done
-  # Same post-processing that is required for AIX mode.
-  aix_post_process_depfile
-  ;;
-
-msvc7)
-  if test "$libtool" = yes; then
-    showIncludes=-Wc,-showIncludes
-  else
-    showIncludes=-showIncludes
-  fi
-  "$@" $showIncludes > "$tmpdepfile"
-  stat=$?
-  grep -v '^Note: including file: ' "$tmpdepfile"
-  if test $stat -ne 0; then
-    rm -f "$tmpdepfile"
-    exit $stat
-  fi
-  rm -f "$depfile"
-  echo "$object : \\" > "$depfile"
-  # The first sed program below extracts the file names and escapes
-  # backslashes for cygpath.  The second sed program outputs the file
-  # name when reading, but also accumulates all include files in the
-  # hold buffer in order to output them again at the end.  This only
-  # works with sed implementations that can handle large buffers.
-  sed < "$tmpdepfile" -n '
-/^Note: including file:  *\(.*\)/ {
-  s//\1/
-  s/\\/\\\\/g
-  p
-}' | $cygpath_u | sort -u | sed -n '
-s/ /\\ /g
-s/\(.*\)/'"$tab"'\1 \\/p
-s/.\(.*\) \\/\1:/
-H
-$ {
-  s/.*/'"$tab"'/
-  G
-  p
-}' >> "$depfile"
-  echo >> "$depfile" # make sure the fragment doesn't end with a backslash
-  rm -f "$tmpdepfile"
-  ;;
-
-msvc7msys)
-  # This case exists only to let depend.m4 do its work.  It works by
-  # looking at the text of this script.  This case will never be run,
-  # since it is checked for above.
-  exit 1
-  ;;
-
-#nosideeffect)
-  # This comment above is used by automake to tell side-effect
-  # dependency tracking mechanisms from slower ones.
-
-dashmstdout)
-  # Important note: in order to support this mode, a compiler *must*
-  # always write the preprocessed file to stdout, regardless of -o.
-  "$@" || exit $?
-
-  # Remove the call to Libtool.
-  if test "$libtool" = yes; then
-    while test "X$1" != 'X--mode=compile'; do
-      shift
-    done
-    shift
-  fi
-
-  # Remove '-o $object'.
-  IFS=" "
-  for arg
-  do
-    case $arg in
-    -o)
-      shift
-      ;;
-    $object)
-      shift
-      ;;
-    *)
-      set fnord "$@" "$arg"
-      shift # fnord
-      shift # $arg
-      ;;
-    esac
-  done
-
-  test -z "$dashmflag" && dashmflag=-M
-  # Require at least two characters before searching for ':'
-  # in the target name.  This is to cope with DOS-style filenames:
-  # a dependency such as 'c:/foo/bar' could be seen as target 'c' otherwise.
-  "$@" $dashmflag |
-    sed "s|^[$tab ]*[^:$tab ][^:][^:]*:[$tab ]*|$object: |" > "$tmpdepfile"
-  rm -f "$depfile"
-  cat < "$tmpdepfile" > "$depfile"
-  # Some versions of the HPUX 10.20 sed can't process this sed invocation
-  # correctly.  Breaking it into two sed invocations is a workaround.
-  tr ' ' "$nl" < "$tmpdepfile" \
-    | sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' \
-    | sed -e 's/$/ :/' >> "$depfile"
-  rm -f "$tmpdepfile"
-  ;;
-
-dashXmstdout)
-  # This case only exists to satisfy depend.m4.  It is never actually
-  # run, as this mode is specially recognized in the preamble.
-  exit 1
-  ;;
-
-makedepend)
-  "$@" || exit $?
-  # Remove any Libtool call
-  if test "$libtool" = yes; then
-    while test "X$1" != 'X--mode=compile'; do
-      shift
-    done
-    shift
-  fi
-  # X makedepend
-  shift
-  cleared=no eat=no
-  for arg
-  do
-    case $cleared in
-    no)
-      set ""; shift
-      cleared=yes ;;
-    esac
-    if test $eat = yes; then
-      eat=no
-      continue
-    fi
-    case "$arg" in
-    -D*|-I*)
-      set fnord "$@" "$arg"; shift ;;
-    # Strip any option that makedepend may not understand.  Remove
-    # the object too, otherwise makedepend will parse it as a source file.
-    -arch)
-      eat=yes ;;
-    -*|$object)
-      ;;
-    *)
-      set fnord "$@" "$arg"; shift ;;
-    esac
-  done
-  obj_suffix=`echo "$object" | sed 's/^.*\././'`
-  touch "$tmpdepfile"
-  ${MAKEDEPEND-makedepend} -o"$obj_suffix" -f"$tmpdepfile" "$@"
-  rm -f "$depfile"
-  # makedepend may prepend the VPATH from the source file name to the object.
-  # No need to regex-escape $object, excess matching of '.' is harmless.
-  sed "s|^.*\($object *:\)|\1|" "$tmpdepfile" > "$depfile"
-  # Some versions of the HPUX 10.20 sed can't process the last invocation
-  # correctly.  Breaking it into two sed invocations is a workaround.
-  sed '1,2d' "$tmpdepfile" \
-    | tr ' ' "$nl" \
-    | sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' \
-    | sed -e 's/$/ :/' >> "$depfile"
-  rm -f "$tmpdepfile" "$tmpdepfile".bak
-  ;;
-
-cpp)
-  # Important note: in order to support this mode, a compiler *must*
-  # always write the preprocessed file to stdout.
-  "$@" || exit $?
-
-  # Remove the call to Libtool.
-  if test "$libtool" = yes; then
-    while test "X$1" != 'X--mode=compile'; do
-      shift
-    done
-    shift
-  fi
-
-  # Remove '-o $object'.
-  IFS=" "
-  for arg
-  do
-    case $arg in
-    -o)
-      shift
-      ;;
-    $object)
-      shift
-      ;;
-    *)
-      set fnord "$@" "$arg"
-      shift # fnord
-      shift # $arg
-      ;;
-    esac
-  done
-
-  "$@" -E \
-    | sed -n -e '/^# [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \
-             -e '/^#line [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \
-    | sed '$ s: \\$::' > "$tmpdepfile"
-  rm -f "$depfile"
-  echo "$object : \\" > "$depfile"
-  cat < "$tmpdepfile" >> "$depfile"
-  sed < "$tmpdepfile" '/^$/d;s/^ //;s/ \\$//;s/$/ :/' >> "$depfile"
-  rm -f "$tmpdepfile"
-  ;;
-
-msvisualcpp)
-  # Important note: in order to support this mode, a compiler *must*
-  # always write the preprocessed file to stdout.
-  "$@" || exit $?
-
-  # Remove the call to Libtool.
-  if test "$libtool" = yes; then
-    while test "X$1" != 'X--mode=compile'; do
-      shift
-    done
-    shift
-  fi
-
-  IFS=" "
-  for arg
-  do
-    case "$arg" in
-    -o)
-      shift
-      ;;
-    $object)
-      shift
-      ;;
-    "-Gm"|"/Gm"|"-Gi"|"/Gi"|"-ZI"|"/ZI")
-        set fnord "$@"
-        shift
-        shift
-        ;;
-    *)
-        set fnord "$@" "$arg"
-        shift
-        shift
-        ;;
-    esac
-  done
-  "$@" -E 2>/dev/null |
-  sed -n '/^#line [0-9][0-9]* "\([^"]*\)"/ s::\1:p' | $cygpath_u | sort -u > "$tmpdepfile"
-  rm -f "$depfile"
-  echo "$object : \\" > "$depfile"
-  sed < "$tmpdepfile" -n -e 's% %\\ %g' -e '/^\(.*\)$/ s::'"$tab"'\1 \\:p' >> "$depfile"
-  echo "$tab" >> "$depfile"
-  sed < "$tmpdepfile" -n -e 's% %\\ %g' -e '/^\(.*\)$/ s::\1\::p' >> "$depfile"
-  rm -f "$tmpdepfile"
-  ;;
-
-msvcmsys)
-  # This case exists only to let depend.m4 do its work.  It works by
-  # looking at the text of this script.  This case will never be run,
-  # since it is checked for above.
-  exit 1
-  ;;
-
-none)
-  exec "$@"
-  ;;
-
-*)
-  echo "Unknown depmode $depmode" 1>&2
-  exit 1
-  ;;
-esac
-
-exit 0
-
-# Local Variables:
-# mode: shell-script
-# sh-indentation: 2
-# eval: (add-hook 'write-file-hooks 'time-stamp)
-# time-stamp-start: "scriptversion="
-# time-stamp-format: "%:y-%02m-%02d.%02H"
-# time-stamp-time-zone: "UTC"
-# time-stamp-end: "; # UTC"
-# End:
@@ -1,501 +0,0 @@
-#!/bin/sh
-# install - install a program, script, or datafile
-
-scriptversion=2013-12-25.23; # UTC
-
-# This originates from X11R5 (mit/util/scripts/install.sh), which was
-# later released in X11R6 (xc/config/util/install.sh) with the
-# following copyright and license.
-#
-# Copyright (C) 1994 X Consortium
-#
-# Permission is hereby granted, free of charge, to any person obtaining a copy
-# of this software and associated documentation files (the "Software"), to
-# deal in the Software without restriction, including without limitation the
-# rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
-# sell copies of the Software, and to permit persons to whom the Software is
-# furnished to do so, subject to the following conditions:
-#
-# The above copyright notice and this permission notice shall be included in
-# all copies or substantial portions of the Software.
-#
-# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
-# X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
-# AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC-
-# TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-#
-# Except as contained in this notice, the name of the X Consortium shall not
-# be used in advertising or otherwise to promote the sale, use or other deal-
-# ings in this Software without prior written authorization from the X Consor-
-# tium.
-#
-#
-# FSF changes to this file are in the public domain.
-#
-# Calling this script install-sh is preferred over install.sh, to prevent
-# 'make' implicit rules from creating a file called install from it
-# when there is no Makefile.
-#
-# This script is compatible with the BSD install script, but was written
-# from scratch.
-
-tab='	'
-nl='
-'
-IFS=" $tab$nl"
-
-# Set DOITPROG to "echo" to test this script.
-
-doit=${DOITPROG-}
-doit_exec=${doit:-exec}
-
-# Put in absolute file names if you don't have them in your path;
-# or use environment vars.
-
-chgrpprog=${CHGRPPROG-chgrp}
-chmodprog=${CHMODPROG-chmod}
-chownprog=${CHOWNPROG-chown}
-cmpprog=${CMPPROG-cmp}
-cpprog=${CPPROG-cp}
-mkdirprog=${MKDIRPROG-mkdir}
-mvprog=${MVPROG-mv}
-rmprog=${RMPROG-rm}
-stripprog=${STRIPPROG-strip}
-
-posix_mkdir=
-
-# Desired mode of installed file.
-mode=0755
-
-chgrpcmd=
-chmodcmd=$chmodprog
-chowncmd=
-mvcmd=$mvprog
-rmcmd="$rmprog -f"
-stripcmd=
-
-src=
-dst=
-dir_arg=
-dst_arg=
-
-copy_on_change=false
-is_target_a_directory=possibly
-
-usage="\
-Usage: $0 [OPTION]... [-T] SRCFILE DSTFILE
-   or: $0 [OPTION]... SRCFILES... DIRECTORY
-   or: $0 [OPTION]... -t DIRECTORY SRCFILES...
-   or: $0 [OPTION]... -d DIRECTORIES...
-
-In the 1st form, copy SRCFILE to DSTFILE.
-In the 2nd and 3rd, copy all SRCFILES to DIRECTORY.
-In the 4th, create DIRECTORIES.
-
-Options:
-     --help     display this help and exit.
-     --version  display version info and exit.
-
-  -c            (ignored)
-  -C            install only if different (preserve the last data modification time)
-  -d            create directories instead of installing files.
-  -g GROUP      $chgrpprog installed files to GROUP.
-  -m MODE       $chmodprog installed files to MODE.
-  -o USER       $chownprog installed files to USER.
-  -s            $stripprog installed files.
-  -t DIRECTORY  install into DIRECTORY.
-  -T            report an error if DSTFILE is a directory.
-
-Environment variables override the default commands:
-  CHGRPPROG CHMODPROG CHOWNPROG CMPPROG CPPROG MKDIRPROG MVPROG
-  RMPROG STRIPPROG
-"
-
-while test $# -ne 0; do
-  case $1 in
-    -c) ;;
-
-    -C) copy_on_change=true;;
-
-    -d) dir_arg=true;;
-
-    -g) chgrpcmd="$chgrpprog $2"
-        shift;;
-
-    --help) echo "$usage"; exit $?;;
-
-    -m) mode=$2
-        case $mode in
-          *' '* | *"$tab"* | *"$nl"* | *'*'* | *'?'* | *'['*)
-            echo "$0: invalid mode: $mode" >&2
-            exit 1;;
-        esac
-        shift;;
-
-    -o) chowncmd="$chownprog $2"
-        shift;;
-
-    -s) stripcmd=$stripprog;;
-
-    -t)
-        is_target_a_directory=always
-        dst_arg=$2
-        # Protect names problematic for 'test' and other utilities.
-        case $dst_arg in
-          -* | [=\(\)!]) dst_arg=./$dst_arg;;
-        esac
-        shift;;
-
-    -T) is_target_a_directory=never;;
-
-    --version) echo "$0 $scriptversion"; exit $?;;
-
-    --) shift
-        break;;
-
-    -*) echo "$0: invalid option: $1" >&2
-        exit 1;;
-
-    *)  break;;
-  esac
-  shift
-done
-
-# We allow the use of options -d and -T together, by making -d
-# take the precedence; this is for compatibility with GNU install.
-
-if test -n "$dir_arg"; then
-  if test -n "$dst_arg"; then
-    echo "$0: target directory not allowed when installing a directory." >&2
-    exit 1
-  fi
-fi
-
-if test $# -ne 0 && test -z "$dir_arg$dst_arg"; then
-  # When -d is used, all remaining arguments are directories to create.
-  # When -t is used, the destination is already specified.
-  # Otherwise, the last argument is the destination.  Remove it from $@.
-  for arg
-  do
-    if test -n "$dst_arg"; then
-      # $@ is not empty: it contains at least $arg.
-      set fnord "$@" "$dst_arg"
-      shift # fnord
-    fi
-    shift # arg
-    dst_arg=$arg
-    # Protect names problematic for 'test' and other utilities.
-    case $dst_arg in
-      -* | [=\(\)!]) dst_arg=./$dst_arg;;
-    esac
-  done
-fi
-
-if test $# -eq 0; then
-  if test -z "$dir_arg"; then
-    echo "$0: no input file specified." >&2
-    exit 1
-  fi
-  # It's OK to call 'install-sh -d' without argument.
-  # This can happen when creating conditional directories.
-  exit 0
-fi
-
-if test -z "$dir_arg"; then
-  if test $# -gt 1 || test "$is_target_a_directory" = always; then
-    if test ! -d "$dst_arg"; then
-      echo "$0: $dst_arg: Is not a directory." >&2
-      exit 1
-    fi
-  fi
-fi
-
-if test -z "$dir_arg"; then
-  do_exit='(exit $ret); exit $ret'
-  trap "ret=129; $do_exit" 1
-  trap "ret=130; $do_exit" 2
-  trap "ret=141; $do_exit" 13
-  trap "ret=143; $do_exit" 15
-
-  # Set umask so as not to create temps with too-generous modes.
-  # However, 'strip' requires both read and write access to temps.
-  case $mode in
-    # Optimize common cases.
-    *644) cp_umask=133;;
-    *755) cp_umask=22;;
-
-    *[0-7])
-      if test -z "$stripcmd"; then
-        u_plus_rw=
-      else
-        u_plus_rw='% 200'
-      fi
-      cp_umask=`expr '(' 777 - $mode % 1000 ')' $u_plus_rw`;;
-    *)
-      if test -z "$stripcmd"; then
-        u_plus_rw=
-      else
-        u_plus_rw=,u+rw
-      fi
-      cp_umask=$mode$u_plus_rw;;
-  esac
-fi
-
-for src
-do
-  # Protect names problematic for 'test' and other utilities.
-  case $src in
-    -* | [=\(\)!]) src=./$src;;
-  esac
-
-  if test -n "$dir_arg"; then
-    dst=$src
-    dstdir=$dst
-    test -d "$dstdir"
-    dstdir_status=$?
-  else
-
-    # Waiting for this to be detected by the "$cpprog $src $dsttmp" command
-    # might cause directories to be created, which would be especially bad
-    # if $src (and thus $dsttmp) contains '*'.
-    if test ! -f "$src" && test ! -d "$src"; then
-      echo "$0: $src does not exist." >&2
-      exit 1
-    fi
-
-    if test -z "$dst_arg"; then
-      echo "$0: no destination specified." >&2
-      exit 1
-    fi
-    dst=$dst_arg
-
-    # If destination is a directory, append the input filename; won't work
-    # if double slashes aren't ignored.
-    if test -d "$dst"; then
-      if test "$is_target_a_directory" = never; then
-        echo "$0: $dst_arg: Is a directory" >&2
-        exit 1
-      fi
-      dstdir=$dst
-      dst=$dstdir/`basename "$src"`
-      dstdir_status=0
-    else
-      dstdir=`dirname "$dst"`
-      test -d "$dstdir"
-      dstdir_status=$?
-    fi
-  fi
-
-  obsolete_mkdir_used=false
-
-  if test $dstdir_status != 0; then
-    case $posix_mkdir in
-      '')
-        # Create intermediate dirs using mode 755 as modified by the umask.
-        # This is like FreeBSD 'install' as of 1997-10-28.
-        umask=`umask`
-        case $stripcmd.$umask in
-          # Optimize common cases.
-          *[2367][2367]) mkdir_umask=$umask;;
-          .*0[02][02] | .[02][02] | .[02]) mkdir_umask=22;;
-
-          *[0-7])
-            mkdir_umask=`expr $umask + 22 \
-              - $umask % 100 % 40 + $umask % 20 \
-              - $umask % 10 % 4 + $umask % 2
-            `;;
-          *) mkdir_umask=$umask,go-w;;
-        esac
-
-        # With -d, create the new directory with the user-specified mode.
-        # Otherwise, rely on $mkdir_umask.
-        if test -n "$dir_arg"; then
-          mkdir_mode=-m$mode
-        else
-          mkdir_mode=
-        fi
-
-        posix_mkdir=false
-        case $umask in
-          *[123567][0-7][0-7])
-            # POSIX mkdir -p sets u+wx bits regardless of umask, which
-            # is incompatible with FreeBSD 'install' when (umask & 300) != 0.
-            ;;
-          *)
-            tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
-            trap 'ret=$?; rmdir "$tmpdir/d" "$tmpdir" 2>/dev/null; exit $ret' 0
-
-            if (umask $mkdir_umask &&
-                exec $mkdirprog $mkdir_mode -p -- "$tmpdir/d") >/dev/null 2>&1
-            then
-              if test -z "$dir_arg" || {
-                   # Check for POSIX incompatibilities with -m.
-                   # HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
-                   # other-writable bit of parent directory when it shouldn't.
-                   # FreeBSD 6.1 mkdir -m -p sets mode of existing directory.
-                   ls_ld_tmpdir=`ls -ld "$tmpdir"`
-                   case $ls_ld_tmpdir in
-                     d????-?r-*) different_mode=700;;
-                     d????-?--*) different_mode=755;;
-                     *) false;;
-                   esac &&
-                   $mkdirprog -m$different_mode -p -- "$tmpdir" && {
-                     ls_ld_tmpdir_1=`ls -ld "$tmpdir"`
-                     test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1"
-                   }
-                 }
-              then posix_mkdir=:
-              fi
-              rmdir "$tmpdir/d" "$tmpdir"
-            else
-              # Remove any dirs left behind by ancient mkdir implementations.
-              rmdir ./$mkdir_mode ./-p ./-- 2>/dev/null
-            fi
-            trap '' 0;;
-        esac;;
-    esac
-
-    if
-      $posix_mkdir && (
-        umask $mkdir_umask &&
-        $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir"
-      )
-    then :
-    else
-
-      # The umask is ridiculous, or mkdir does not conform to POSIX,
-      # or it failed possibly due to a race condition.  Create the
-      # directory the slow way, step by step, checking for races as we go.
-
-      case $dstdir in
-        /*) prefix='/';;
-        [-=\(\)!]*) prefix='./';;
-        *)  prefix='';;
-      esac
-
-      oIFS=$IFS
-      IFS=/
-      set -f
-      set fnord $dstdir
-      shift
-      set +f
-      IFS=$oIFS
-
-      prefixes=
-
-      for d
-      do
-        test X"$d" = X && continue
-
-        prefix=$prefix$d
-        if test -d "$prefix"; then
-          prefixes=
-        else
-          if $posix_mkdir; then
-            (umask=$mkdir_umask &&
-             $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir") && break
-            # Don't fail if two instances are running concurrently.
-            test -d "$prefix" || exit 1
-          else
-            case $prefix in
-              *\'*) qprefix=`echo "$prefix" | sed "s/'/'\\\\\\\\''/g"`;;
-              *) qprefix=$prefix;;
-            esac
-            prefixes="$prefixes '$qprefix'"
-          fi
-        fi
-        prefix=$prefix/
-      done
-
-      if test -n "$prefixes"; then
-        # Don't fail if two instances are running concurrently.
-        (umask $mkdir_umask &&
-         eval "\$doit_exec \$mkdirprog $prefixes") ||
-          test -d "$dstdir" || exit 1
-        obsolete_mkdir_used=true
-      fi
-    fi
-  fi
-
-  if test -n "$dir_arg"; then
-    { test -z "$chowncmd" || $doit $chowncmd "$dst"; } &&
-    { test -z "$chgrpcmd" || $doit $chgrpcmd "$dst"; } &&
-    { test "$obsolete_mkdir_used$chowncmd$chgrpcmd" = false ||
-      test -z "$chmodcmd" || $doit $chmodcmd $mode "$dst"; } || exit 1
-  else
-
-    # Make a couple of temp file names in the proper directory.
-    dsttmp=$dstdir/_inst.$$_
-    rmtmp=$dstdir/_rm.$$_
-
-    # Trap to clean up those temp files at exit.
-    trap 'ret=$?; rm -f "$dsttmp" "$rmtmp" && exit $ret' 0
-
-    # Copy the file name to the temp name.
-    (umask $cp_umask && $doit_exec $cpprog "$src" "$dsttmp") &&
-
-    # and set any options; do chmod last to preserve setuid bits.
-    #
-    # If any of these fail, we abort the whole thing.  If we want to
-    # ignore errors from any of these, just make sure not to ignore
-    # errors from the above "$doit $cpprog $src $dsttmp" command.
-    #
-    { test -z "$chowncmd" || $doit $chowncmd "$dsttmp"; } &&
-    { test -z "$chgrpcmd" || $doit $chgrpcmd "$dsttmp"; } &&
-    { test -z "$stripcmd" || $doit $stripcmd "$dsttmp"; } &&
-    { test -z "$chmodcmd" || $doit $chmodcmd $mode "$dsttmp"; } &&
-
-    # If -C, don't bother to copy if it wouldn't change the file.
-    if $copy_on_change &&
-       old=`LC_ALL=C ls -dlL "$dst"     2>/dev/null` &&
-       new=`LC_ALL=C ls -dlL "$dsttmp"  2>/dev/null` &&
-       set -f &&
-       set X $old && old=:$2:$4:$5:$6 &&
-       set X $new && new=:$2:$4:$5:$6 &&
-       set +f &&
-       test "$old" = "$new" &&
-       $cmpprog "$dst" "$dsttmp" >/dev/null 2>&1
-    then
-      rm -f "$dsttmp"
-    else
-      # Rename the file to the real destination.
-      $doit $mvcmd -f "$dsttmp" "$dst" 2>/dev/null ||
-
-      # The rename failed, perhaps because mv can't rename something else
-      # to itself, or perhaps because mv is so ancient that it does not
-      # support -f.
-      {
-        # Now remove or move aside any old file at destination location.
-        # We try this two ways since rm can't unlink itself on some
-        # systems and the destination file might be busy for other
-        # reasons.  In this case, the final cleanup might fail but the new
-        # file should still install successfully.
-        {
-          test ! -f "$dst" ||
-          $doit $rmcmd -f "$dst" 2>/dev/null ||
-          { $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null &&
-            { $doit $rmcmd -f "$rmtmp" 2>/dev/null; :; }
-          } ||
-          { echo "$0: cannot unlink or rename $dst" >&2
-            (exit 1); exit 1
-          }
-        } &&
-
-        # Now rename the file to the real destination.
-        $doit $mvcmd "$dsttmp" "$dst"
-      }
-    fi || exit 1
-
-    trap '' 0
-  fi
-done
-
-# Local variables:
-# eval: (add-hook 'write-file-hooks 'time-stamp)
-# time-stamp-start: "scriptversion="
-# time-stamp-format: "%:y-%02m-%02d.%02H"
-# time-stamp-time-zone: "UTC"
-# time-stamp-end: "; # UTC"
-# End:
@@ -1,215 +0,0 @@
-#! /bin/sh
-# Common wrapper for a few potentially missing GNU programs.
-
-scriptversion=2013-10-28.13; # UTC
-
-# Copyright (C) 1996-2014 Free Software Foundation, Inc.
-# Originally written by Fran,cois Pinard <[email protected]>, 1996.
-
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
-
-# You should have received a copy of the GNU General Public License
-# along with this program.  If not, see <http://www.gnu.org/licenses/>.
-
-# As a special exception to the GNU General Public License, if you
-# distribute this file as part of a program that contains a
-# configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-if test $# -eq 0; then
-  echo 1>&2 "Try '$0 --help' for more information"
-  exit 1
-fi
-
-case $1 in
-
-  --is-lightweight)
-    # Used by our autoconf macros to check whether the available missing
-    # script is modern enough.
-    exit 0
-    ;;
-
-  --run)
-    # Back-compat with the calling convention used by older automake.
-    shift
-    ;;
-
-  -h|--h|--he|--hel|--help)
-    echo "\
-$0 [OPTION]... PROGRAM [ARGUMENT]...
-
-Run 'PROGRAM [ARGUMENT]...', returning a proper advice when this fails due
-to PROGRAM being missing or too old.
-
-Options:
-  -h, --help      display this help and exit
-  -v, --version   output version information and exit
-
-Supported PROGRAM values:
-  aclocal   autoconf  autoheader   autom4te  automake  makeinfo
-  bison     yacc      flex         lex       help2man
-
-Version suffixes to PROGRAM as well as the prefixes 'gnu-', 'gnu', and
-'g' are ignored when checking the name.
-
-Send bug reports to <[email protected]>."
-    exit $?
-    ;;
-
-  -v|--v|--ve|--ver|--vers|--versi|--versio|--version)
-    echo "missing $scriptversion (GNU Automake)"
-    exit $?
-    ;;
-
-  -*)
-    echo 1>&2 "$0: unknown '$1' option"
-    echo 1>&2 "Try '$0 --help' for more information"
-    exit 1
-    ;;
-
-esac
-
-# Run the given program, remember its exit status.
-"$@"; st=$?
-
-# If it succeeded, we are done.
-test $st -eq 0 && exit 0
-
-# Also exit now if we it failed (or wasn't found), and '--version' was
-# passed; such an option is passed most likely to detect whether the
-# program is present and works.
-case $2 in --version|--help) exit $st;; esac
-
-# Exit code 63 means version mismatch.  This often happens when the user
-# tries to use an ancient version of a tool on a file that requires a
-# minimum version.
-if test $st -eq 63; then
-  msg="probably too old"
-elif test $st -eq 127; then
-  # Program was missing.
-  msg="missing on your system"
-else
-  # Program was found and executed, but failed.  Give up.
-  exit $st
-fi
-
-perl_URL=http://www.perl.org/
-flex_URL=http://flex.sourceforge.net/
-gnu_software_URL=http://www.gnu.org/software
-
-program_details ()
-{
-  case $1 in
-    aclocal|automake)
-      echo "The '$1' program is part of the GNU Automake package:"
-      echo "<$gnu_software_URL/automake>"
-      echo "It also requires GNU Autoconf, GNU m4 and Perl in order to run:"
-      echo "<$gnu_software_URL/autoconf>"
-      echo "<$gnu_software_URL/m4/>"
-      echo "<$perl_URL>"
-      ;;
-    autoconf|autom4te|autoheader)
-      echo "The '$1' program is part of the GNU Autoconf package:"
-      echo "<$gnu_software_URL/autoconf/>"
-      echo "It also requires GNU m4 and Perl in order to run:"
-      echo "<$gnu_software_URL/m4/>"
-      echo "<$perl_URL>"
-      ;;
-  esac
-}
-
-give_advice ()
-{
-  # Normalize program name to check for.
-  normalized_program=`echo "$1" | sed '
-    s/^gnu-//; t
-    s/^gnu//; t
-    s/^g//; t'`
-
-  printf '%s\n' "'$1' is $msg."
-
-  configure_deps="'configure.ac' or m4 files included by 'configure.ac'"
-  case $normalized_program in
-    autoconf*)
-      echo "You should only need it if you modified 'configure.ac',"
-      echo "or m4 files included by it."
-      program_details 'autoconf'
-      ;;
-    autoheader*)
-      echo "You should only need it if you modified 'acconfig.h' or"
-      echo "$configure_deps."
-      program_details 'autoheader'
-      ;;
-    automake*)
-      echo "You should only need it if you modified 'Makefile.am' or"
-      echo "$configure_deps."
-      program_details 'automake'
-      ;;
-    aclocal*)
-      echo "You should only need it if you modified 'acinclude.m4' or"
-      echo "$configure_deps."
-      program_details 'aclocal'
-      ;;
-   autom4te*)
-      echo "You might have modified some maintainer files that require"
-      echo "the 'autom4te' program to be rebuilt."
-      program_details 'autom4te'
-      ;;
-    bison*|yacc*)
-      echo "You should only need it if you modified a '.y' file."
-      echo "You may want to install the GNU Bison package:"
-      echo "<$gnu_software_URL/bison/>"
-      ;;
-    lex*|flex*)
-      echo "You should only need it if you modified a '.l' file."
-      echo "You may want to install the Fast Lexical Analyzer package:"
-      echo "<$flex_URL>"
-      ;;
-    help2man*)
-      echo "You should only need it if you modified a dependency" \
-           "of a man page."
-      echo "You may want to install the GNU Help2man package:"
-      echo "<$gnu_software_URL/help2man/>"
-    ;;
-    makeinfo*)
-      echo "You should only need it if you modified a '.texi' file, or"
-      echo "any other file indirectly affecting the aspect of the manual."
-      echo "You might want to install the Texinfo package:"
-      echo "<$gnu_software_URL/texinfo/>"
-      echo "The spurious makeinfo call might also be the consequence of"
-      echo "using a buggy 'make' (AIX, DU, IRIX), in which case you might"
-      echo "want to install GNU make:"
-      echo "<$gnu_software_URL/make/>"
-      ;;
-    *)
-      echo "You might have modified some files without having the proper"
-      echo "tools for further handling them.  Check the 'README' file, it"
-      echo "often tells you about the needed prerequisites for installing"
-      echo "this package.  You may also peek at any GNU archive site, in"
-      echo "case some other package contains this missing '$1' program."
-      ;;
-  esac
-}
-
-give_advice "$1" | sed -e '1s/^/WARNING: /' \
-                       -e '2,$s/^/         /' >&2
-
-# Propagate the correct exit status (expected to be 127 for a program
-# not found, 63 for a program that failed due to version mismatch).
-exit $st
-
-# Local variables:
-# eval: (add-hook 'write-file-hooks 'time-stamp)
-# time-stamp-start: "scriptversion="
-# time-stamp-format: "%:y-%02m-%02d.%02H"
-# time-stamp-time-zone: "UTC"
-# time-stamp-end: "; # UTC"
-# End:
@@ -1,3 +0,0 @@
-#!/bin/sh
-# -E to keep the environment variables needed to run the tests.
-exec sudo -E "$@"
@@ -1,148 +0,0 @@
-#! /bin/sh
-# test-driver - basic testsuite driver script.
-
-scriptversion=2013-07-13.22; # UTC
-
-# Copyright (C) 2011-2014 Free Software Foundation, Inc.
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program.  If not, see <http://www.gnu.org/licenses/>.
-
-# As a special exception to the GNU General Public License, if you
-# distribute this file as part of a program that contains a
-# configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-# This file is maintained in Automake, please report
-# bugs to <[email protected]> or send patches to
-# <[email protected]>.
-
-# Make unconditional expansion of undefined variables an error.  This
-# helps a lot in preventing typo-related bugs.
-set -u
-
-usage_error ()
-{
-  echo "$0: $*" >&2
-  print_usage >&2
-  exit 2
-}
-
-print_usage ()
-{
-  cat <<END
-Usage:
-  test-driver --test-name=NAME --log-file=PATH --trs-file=PATH
-              [--expect-failure={yes|no}] [--color-tests={yes|no}]
-              [--enable-hard-errors={yes|no}] [--]
-              TEST-SCRIPT [TEST-SCRIPT-ARGUMENTS]
-The '--test-name', '--log-file' and '--trs-file' options are mandatory.
-END
-}
-
-test_name= # Used for reporting.
-log_file=  # Where to save the output of the test script.
-trs_file=  # Where to save the metadata of the test run.
-expect_failure=no
-color_tests=no
-enable_hard_errors=yes
-while test $# -gt 0; do
-  case $1 in
-  --help) print_usage; exit $?;;
-  --version) echo "test-driver $scriptversion"; exit $?;;
-  --test-name) test_name=$2; shift;;
-  --log-file) log_file=$2; shift;;
-  --trs-file) trs_file=$2; shift;;
-  --color-tests) color_tests=$2; shift;;
-  --expect-failure) expect_failure=$2; shift;;
-  --enable-hard-errors) enable_hard_errors=$2; shift;;
-  --) shift; break;;
-  -*) usage_error "invalid option: '$1'";;
-   *) break;;
-  esac
-  shift
-done
-
-missing_opts=
-test x"$test_name" = x && missing_opts="$missing_opts --test-name"
-test x"$log_file"  = x && missing_opts="$missing_opts --log-file"
-test x"$trs_file"  = x && missing_opts="$missing_opts --trs-file"
-if test x"$missing_opts" != x; then
-  usage_error "the following mandatory options are missing:$missing_opts"
-fi
-
-if test $# -eq 0; then
-  usage_error "missing argument"
-fi
-
-if test $color_tests = yes; then
-  # Keep this in sync with 'lib/am/check.am:$(am__tty_colors)'.
-  red='[0;31m' # Red.
-  grn='[0;32m' # Green.
-  lgn='[1;32m' # Light green.
-  blu='[1;34m' # Blue.
-  mgn='[0;35m' # Magenta.
-  std='[m'     # No color.
-else
-  red= grn= lgn= blu= mgn= std=
-fi
-
-do_exit='rm -f $log_file $trs_file; (exit $st); exit $st'
-trap "st=129; $do_exit" 1
-trap "st=130; $do_exit" 2
-trap "st=141; $do_exit" 13
-trap "st=143; $do_exit" 15
-
-# Test script is run here.
-"$@" >$log_file 2>&1
-estatus=$?
-
-if test $enable_hard_errors = no && test $estatus -eq 99; then
-  tweaked_estatus=1
-else
-  tweaked_estatus=$estatus
-fi
-
-case $tweaked_estatus:$expect_failure in
-  0:yes) col=$red res=XPASS recheck=yes gcopy=yes;;
-  0:*)   col=$grn res=PASS  recheck=no  gcopy=no;;
-  77:*)  col=$blu res=SKIP  recheck=no  gcopy=yes;;
-  99:*)  col=$mgn res=ERROR recheck=yes gcopy=yes;;
-  *:yes) col=$lgn res=XFAIL recheck=no  gcopy=yes;;
-  *:*)   col=$red res=FAIL  recheck=yes gcopy=yes;;
-esac
-
-# Report the test outcome and exit status in the logs, so that one can
-# know whether the test passed or failed simply by looking at the '.log'
-# file, without the need of also peaking into the corresponding '.trs'
-# file (automake bug#11814).
-echo "$res $test_name (exit status: $estatus)" >>$log_file
-
-# Report outcome to console.
-echo "${col}${res}${std}: $test_name"
-
-# Register the test result, and other relevant metadata.
-echo ":test-result: $res" > $trs_file
-echo ":global-test-result: $res" >> $trs_file
-echo ":recheck: $recheck" >> $trs_file
-echo ":copy-in-global-log: $gcopy" >> $trs_file
-
-# Local Variables:
-# mode: shell-script
-# sh-indentation: 2
-# eval: (add-hook 'write-file-hooks 'time-stamp)
-# time-stamp-start: "scriptversion="
-# time-stamp-format: "%:y-%02m-%02d.%02H"
-# time-stamp-time-zone: "UTC"
-# time-stamp-end: "; # UTC"
-# End:
@@ -1,10 +0,0 @@
-prefix=@prefix@
-exec_prefix=@exec_prefix@
-libdir=@libdir@
-includedir=@includedir@/@PACKAGE_NAME@
-
-Name: google-breakpad-client
-Description: An open-source multi-platform crash reporting system
-Version: @PACKAGE_VERSION@
-Libs: -L${libdir} -lbreakpad_client @PTHREAD_LIBS@
-Cflags: -I${includedir} @PTHREAD_CFLAGS@
@@ -1,10 +0,0 @@
-prefix=@prefix@
-exec_prefix=@exec_prefix@
-libdir=@libdir@
-includedir=@includedir@/@PACKAGE_NAME@
-
-Name: google-breakpad
-Description: An open-source multi-platform crash reporting system
-Version: @PACKAGE_VERSION@
-Libs: -L${libdir} -lbreakpad @PTHREAD_LIBS@
-Cflags: -I${includedir} @PTHREAD_CFLAGS@
@@ -1,3 +0,0 @@
-GERRIT_HOST: True
-CODE_REVIEW_SERVER: chromium-review.googlesource.com
-VIEW_VC: https://chromium.googlesource.com/breakpad/breakpad/+/
@@ -1,272 +0,0 @@
-# Copyright (c) 2006, Google Inc.
-# All rights reserved.
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions are
-# met:
-#
-#     * Redistributions of source code must retain the above copyright
-# notice, this list of conditions and the following disclaimer.
-#     * Redistributions in binary form must reproduce the above
-# copyright notice, this list of conditions and the following disclaimer
-# in the documentation and/or other materials provided with the
-# distribution.
-#     * Neither the name of Google Inc. nor the names of its
-# contributors may be used to endorse or promote products derived from
-# this software without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-AC_PREREQ(2.64)
-
-AC_INIT(breakpad, 0.1, [email protected])
-dnl Sanity check: the argument is just a file that should exist.
-AC_CONFIG_SRCDIR(README.md)
-AC_CONFIG_AUX_DIR(autotools)
-AC_CONFIG_MACRO_DIR([m4])
-AC_CANONICAL_HOST
-
-AM_INIT_AUTOMAKE(subdir-objects tar-ustar 1.11.1)
-AM_CONFIG_HEADER(src/config.h)
-AM_MAINTAINER_MODE
-
-AM_PROG_AR
-AM_PROG_AS
-AC_PROG_CC
-AM_PROG_CC_C_O
-AC_PROG_CPP
-AC_PROG_CXX
-AC_PROG_RANLIB
-
-dnl This must come before all the feature tests below.
-AC_ARG_ENABLE(m32,
-              AS_HELP_STRING([--enable-m32],
-                             [Compile/build with -m32]
-                             [(default is no)]),
-              [case "${enableval}" in
-                 yes)
-                   CFLAGS="${CFLAGS} -m32"
-                   CXXFLAGS="${CXXFLAGS} -m32"
-                   usem32=true
-                   ;;
-                 no)
-                   usem32=false
-                   ;;
-                 *)
-                   AC_MSG_ERROR(bad value ${enableval} for --enable-m32)
-                   ;;
-               esac],
-              [usem32=false])
-
-AC_HEADER_STDC
-AC_SYS_LARGEFILE
-AX_PTHREAD
-AC_CHECK_HEADERS([a.out.h sys/mman.h sys/random.h])
-AC_CHECK_FUNCS([arc4random getcontext getrandom memfd_create])
-AM_CONDITIONAL([HAVE_GETCONTEXT], [test "x$ac_cv_func_getcontext" = xyes])
-AM_CONDITIONAL([HAVE_MEMFD_CREATE], [test "x$ac_cv_func_memfd_create" = xyes])
-
-AX_CXX_COMPILE_STDCXX(11, noext, mandatory)
-
-dnl Test supported warning flags.
-WARN_CXXFLAGS=
-dnl This warning flag is used by clang.  Its default behavior is to warn when
-dnl given an unknown flag rather than error out.
-AC_LANG_PUSH([C++])
-AX_CHECK_COMPILE_FLAG([-Werror=unknown-warning-option],[
-  ax_compiler_flags_test="-Werror=unknown-warning-option"
-],[
-  ax_compiler_flags_test=""
-])
-AX_APPEND_COMPILE_FLAGS(m4_flatten([
-  -Wmissing-braces
-  -Wnon-virtual-dtor
-  -Woverloaded-virtual
-  -Wreorder
-  -Wsign-compare
-  -Wunused-local-typedefs
-  -Wunused-variable
-  -Wvla
-]), [WARN_CXXFLAGS], [${ax_compiler_flags_test}])
-AS_VAR_APPEND([WARN_CXXFLAGS], " -Werror")
-AC_LANG_POP([C++])
-AC_SUBST([WARN_CXXFLAGS])
-
-dnl Test support for O_CLOEXEC
-AX_CHECK_DEFINE([fcntl.h], [O_CLOEXEC], [],
-                [AC_DEFINE([O_CLOEXEC], [0], [Fallback definition for old systems])])
-
-# Only build Linux client libs when compiling for Linux
-case $host in
-  *-*-linux* | *-android* )
-    LINUX_HOST=true
-    ;;
-esac
-AM_CONDITIONAL(LINUX_HOST, test x$LINUX_HOST = xtrue)
-
-# Only use Android support headers when compiling for Android
-case $host in
-  *-android*)
-    ANDROID_HOST=true
-    ;;
-esac
-AM_CONDITIONAL(ANDROID_HOST, test x$ANDROID_HOST = xtrue)
-
-# Some tools (like mac ones) only support x86 currently.
-case $host_cpu in
-  i?86|x86_64)
-    X86_HOST=true
-    ;;
-esac
-AM_CONDITIONAL(X86_HOST, test x$X86_HOST = xtrue)
-
-AC_ARG_ENABLE(processor,
-              AS_HELP_STRING([--disable-processor],
-                             [Don't build processor library]
-                             [(default is no)]),
-              [case "${enableval}" in
-                 yes)
-                   disable_processor=false
-                   ;;
-                 no)
-                   disable_processor=true
-                   ;;
-                 *)
-                   AC_MSG_ERROR(bad value ${enableval} for --disable-processor)
-                   ;;
-               esac],
-              [disable_processor=false])
-AM_CONDITIONAL(DISABLE_PROCESSOR, test x$disable_processor = xtrue)
-
-AC_ARG_ENABLE(tools,
-              AS_HELP_STRING([--disable-tools],
-                             [Don't build tool binaries]
-                             [(default is no)]),
-              [case "${enableval}" in
-                 yes)
-                   disable_tools=false
-                   ;;
-                 no)
-                   disable_tools=true
-                   ;;
-                 *)
-                   AC_MSG_ERROR(bad value ${enableval} for --disable-tools)
-                   ;;
-               esac],
-              [disable_tools=false])
-AM_CONDITIONAL(DISABLE_TOOLS, test x$disable_tools = xtrue)
-
-if test x$LINUX_HOST = xfalse -a x$disable_processor = xtrue -a x$disable_tools = xtrue; then
-   AC_MSG_ERROR([--disable-processor and --disable-tools were specified, and not building for Linux. Nothing to build!])
-fi
-
-AC_ARG_ENABLE(system-test-libs,
-              AS_HELP_STRING([--enable-system-test-libs],
-                             [Use gtest/gmock/etc... from the system instead ]
-                             [of the local copies (default is local)]),
-              [case "${enableval}" in
-                 yes)
-                   system_test_libs=true
-                   ;;
-                 no)
-                   system_test_libs=false
-                   ;;
-                 *)
-                   AC_MSG_ERROR(bad value ${enableval} for --enable-system-test-libs)
-                   ;;
-               esac],
-              [system_test_libs=false])
-AM_CONDITIONAL(SYSTEM_TEST_LIBS, test x$system_test_libs = xtrue)
-
-AC_ARG_VAR([GMOCK_CFLAGS], [Compiler flags for gmock])
-AC_ARG_VAR([GMOCK_LIBS], [Linker flags for gmock])
-AC_ARG_VAR([GTEST_CFLAGS], [Compiler flags for gtest])
-AC_ARG_VAR([GTEST_LIBS], [Linker flags for gtest])
-if test x$system_test_libs = xtrue; then
-  : "${GMOCK_CFLAGS:=-pthread}"
-  : "${GMOCK_LIBS:=-lgmock -lgtest -pthread -lpthread}"
-  : "${GTEST_CFLAGS:=-pthread}"
-  : "${GTEST_LIBS:=-lgtest -pthread -lpthread}"
-fi
-
-AC_ARG_ENABLE(selftest,
-              AS_HELP_STRING([--enable-selftest],
-                             [Run extra tests with "make check" ]
-                             [(may conflict with optimizations) ]
-                             [(default is no)]),
-              [case "${enableval}" in
-                 yes)
-                   selftest=true
-                   ;;
-                 no)
-                   selftest=false
-                   ;;
-                 *)
-                   AC_MSG_ERROR(bad value ${enableval} for --enable-selftest)
-                   ;;
-               esac],
-              [selftest=false])
-AM_CONDITIONAL(SELFTEST, test x$selftest = xtrue)
-
-AC_ARG_WITH(rust-demangle,
-            AS_HELP_STRING([--with-rust-demangle=/path/to/rust-demangle-capi],
-                             [Link against the rust-demangle library]
-                             [to demangle Rust language symbols during]
-                             [symbol dumping (default is no)]
-                             [Pass the path to the crate root.]),
-            [case "${withval}" in
-               yes)
-                 AC_MSG_ERROR(You must pass the path to the rust-demangle-capi crate for --with-rust-demangle)
-                 ;;
-               no)
-                 rust_demangle=false
-                 ;;
-               *)
-                 if ! test -f "${withval}/Cargo.toml"; then
-                   AC_MSG_ERROR(You must pass the path to the rust-demangle-capi crate for --with-rust-demangle)
-                 fi
-                 RUST_DEMANGLE_CFLAGS="-DHAVE_RUST_DEMANGLE -I${withval}/target/include"
-                 RUST_DEMANGLE_LIBS="-L${withval}/target/release -lrust_demangle -lpthread -ldl"
-                 ;;
-             esac],
-            [rust_demangle=false])
-AC_ARG_VAR([RUST_DEMANGLE_CFLAGS], [Compiler flags for rust-demangle])
-AC_ARG_VAR([RUST_DEMANGLE_LIBS], [Linker flags for rust-demangle])
-
-AC_ARG_WITH(tests-as-root,
-            AS_HELP_STRING([--with-tests-as-root],
-                           [Run the tests as root. Use this on platforms]
-                           [like travis-ci.org that require root privileges]
-                           [to use ptrace (default is no)]),
-            [case "${withval}" in
-               yes)
-                 tests_as_root=true
-                 ;;
-               no)
-                 tests_as_root=false
-                 ;;
-               *)
-                 AC_MSG_ERROR(--with-tests-as-root can only be "yes" or "no")
-                 ;;
-             esac],
-            [tests_as_root=false])
-AM_CONDITIONAL(TESTS_AS_ROOT, test x$tests_as_root = xtrue)
-
-AC_CONFIG_FILES(m4_flatten([
-  breakpad.pc
-  breakpad-client.pc
-  Makefile
-]))
-
-AC_OUTPUT
@@ -1,43 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!-- AUTOGENERATED BY deps-to-manifest.py; DO NOT EDIT -->
-<manifest>
-
-  <default revision='refs/heads/main'
-           remote='chromium'
-           sync-c='true'
-           sync-j='8' />
-
-  <remote  name='github'
-           fetch='https://github.com/'
-           review='' />
-
-  <remote  name='chromium'
-           fetch='https://chromium.googlesource.com/'
-           review='https://chromium-review.googlesource.com' />
-
-  <project path='src'
-           name='breakpad/breakpad'
-           revision='refs/heads/main'
-           remote='chromium' />
-
-  <project path='src/src/tools/gyp'
-           name='external/gyp/'
-           revision='324dd166b7c0b39d513026fa52d6280ac6d56770'
-           remote='chromium' />
-
-  <project path='src/src/testing'
-           name='google/googletest.git'
-           revision='4fe018038f87675c083d0cfb6a6b57c274fb1753'
-           remote='github' />
-
-  <project path='src/src/third_party/lss'
-           name='linux-syscall-support/'
-           revision='e1e7b0ad8ee99a875b272c8e33e308472e897660'
-           remote='chromium' />
-
-  <project path='src/src/third_party/protobuf/protobuf'
-           name='google/protobuf.git'
-           revision='cb6dd4ef5f82e41e06179dcd57d3b1d9246ad6ac'
-           remote='github' />
-
-</manifest>
@@ -1 +0,0 @@
-*
@@ -1,223 +0,0 @@
-# Breakpad Client Libraries
-
-## Objective
-
-The Breakpad client libraries are responsible for monitoring an application for
-crashes (exceptions), handling them when they occur by generating a dump, and
-providing a means to upload dumps to a crash reporting server. These tasks are
-divided between the “handler” (short for “exception handler”) library linked in
-to an application being monitored for crashes, and the “sender” library,
-intended to be linked in to a separate external program.
-
-## Background
-
-As one of the chief tasks of the client handler is to generate a dump, an
-understanding of [dump files](processor_design.md) will aid in understanding the
-handler.
-
-## Overview
-
-Breakpad provides client libraries for each of its target platforms. Currently,
-these exist for Windows on x86 and Mac OS X on both x86 and PowerPC. A Linux
-implementation has been written and is currently under review.
-
-Because the mechanisms for catching exceptions and the methods for obtaining the
-information that a dump contains vary between operating systems, each target
-operating system requires a completely different handler implementation. Where
-multiple CPUs are supported for a single operating system, the handler
-implementation will likely also require separate code for each processor type to
-extract CPU-specific information. One of the goals of the Breakpad handler is to
-provide a prepackaged cross-platform system that masks many of these
-system-level differences and quirks from the application developer. Although the
-underlying implementations differ, the handler library for each system follows
-the same set of principles and exposes a similar interface.
-
-Code that wishes to take advantage of Breakpad should be linked against the
-handler library, and should, at an appropriate time, install a Breakpad handler.
-For applications, it is generally desirable to install the handler as early in
-the start-up process as possible. Developers of library code using Breakpad to
-monitor itself may wish to install a Breakpad handler when the library is
-loaded, or may only want to install a handler when calls are made in to the
-library.
-
-The handler can be triggered to generate a dump either by catching an exception
-or at the request of the application itself. The latter case may be useful in
-debugging assertions or other conditions where developers want to know how a
-program got in to a specific non-crash state. After generating a dump, the
-handler calls a user-specified callback function. The callback function may
-collect additional data about the program’s state, quit the program, launch a
-crash reporter application, or perform other tasks. Allowing for this
-functionality to be dictated by a callback function preserves flexibility.
-
-The sender library is also has a separate implementation for each supported
-platform, because of the varying interfaces for accessing network resources on
-different operating systems. The sender transmits a dump along with other
-application-defined information to a crash report server via HTTP. Because dumps
-may contain sensitive data, the sender allows for the use of HTTPS.
-
-The canonical example of the entire client system would be for a monitored
-application to link against the handler library, install a Breakpad handler from
-its main function, and provide a callback to launch a small crash reporter
-program. The crash reporter program would be linked against the sender library,
-and would send the crash dump when launched. A separate process is recommended
-for this function because of the unreliability inherent in doing any significant
-amount of work from a crashed process.
-
-## Detailed Design
-
-### Exception Handler Installation
-
-The mechanisms for installing an exception handler vary between operating
-systems. On Windows, it’s a relatively simple matter of making one call to
-register a [top-level exception
-filter](http://msdn.microsoft.com/library/en-us/debug/base/setunhandledexceptionfilter.asp)
-callback function. On most Unix-like systems such as Linux, processes are
-informed of exceptions by the delivery of a signal, so an exception handler
-takes the form of a signal handler. The native mechanism to catch exceptions on
-Mac OS X requires a large amount of code to set up a Mach port, identify it as
-the exception port, and assign a thread to listen for an exception on that port.
-Just as the preparation of exception handlers differ, the manner in which they
-are called differs as well. On Windows and most Unix-like systems, the handler
-is called on the thread that caused the exception. On Mac OS X, the thread
-listening to the exception port is notified that an exception has occurred. The
-different implementations of the Breakpad handler libraries perform these tasks
-in the appropriate ways on each platform, while exposing a similar interface on
-each.
-
-A Breakpad handler is embodied in an `ExceptionHandler` object. Because it’s a
-C++ object, `ExceptionHandler`s may be created as local variables, allowing them
-to be installed and removed as functions are called and return. This provides
-one possible way for a developer to monitor only a portion of an application for
-crashes.
-
-### Exception Basics
-
-Once an application encounters an exception, it is in an indeterminate and
-possibly hazardous state. Consequently, any code that runs after an exception
-occurs must take extreme care to avoid performing operations that might fail,
-hang, or cause additional exceptions. This task is not at all straightforward,
-and the Breakpad handler library seeks to do it properly, accounting for all of
-the minute details while allowing other application developers, even those with
-little systems programming experience, to reap the benefits. All of the Breakpad
-handler code that executes after an exception occurs has been written according
-to the following guidelines for safety at exception time:
-
-*   Use of the application heap is forbidden. The heap may be corrupt or
-    otherwise unusable, and allocators may not function.
-*   Resource allocation must be severely limited. The handler may create a new
-    file to contain the dump, and it may attempt to launch a process to continue
-    handling the crash.
-*   Execution on the thread that caused the exception is significantly limited.
-    The only code permitted to execute on this thread is the code necessary to
-    transition handling to a dedicated preallocated handler thread, and the code
-    to return from the exception handler.
-*   Handlers shouldn’t handle crashes by attempting to walk stacks themselves,
-    as stacks may be in inconsistent states. Dump generation should be performed
-    by interfacing with the operating system’s memory manager and code module
-    manager.
-*   Library code, including runtime library code, must be avoided unless it
-    provably meets the above guidelines. For example, this means that the STL
-    string class may not be used, because it performs operations that attempt to
-    allocate and use heap memory. It also means that many C runtime functions
-    must be avoided, particularly on Windows, because of heap operations that
-    they may perform.
-
-A dedicated handler thread is used to preserve the state of the exception thread
-when an exception occurs: during dump generation, it is difficult if not
-impossible for a thread to accurately capture its own state. Performing all
-exception-handling functions on a separate thread is also critical when handling
-stack-limit-exceeded exceptions. It would be hazardous to run out of stack space
-while attempting to handle an exception. Because of the rule against allocating
-resources at exception time, the Breakpad handler library creates its handler
-thread when it installs its exception handler. On Mac OS X, this handler thread
-is created during the normal setup of the exception handler, and the handler
-thread will be signaled directly in the event of an exception. On Windows and
-Linux, the handler thread is signaled by a small amount of code that executes on
-the exception thread. Because the code that executes on the exception thread in
-this case is small and safe, this does not pose a problem. Even when an
-exception is caused by exceeding stack size limits, this code is sufficiently
-compact to execute entirely within the stack’s guard page without causing an
-exception.
-
-The handler thread may also be triggered directly by a user call, even when no
-exception occurs, to allow dumps to be generated at any point deemed
-interesting.
-
-### Filter Callback
-
-When the handler thread begins handling an exception, it calls an optional
-user-defined filter callback function, which is responsible for judging whether
-Breakpad’s handler should continue handling the exception or not. This mechanism
-is provided for the benefit of library or plug-in code, whose developers may not
-be interested in reports of crashes that occur outside of their modules but
-within processes hosting their code. If the filter callback indicates that it is
-not interested in the exception, the Breakpad handler arranges for it to be
-delivered to any previously-installed handler.
-
-### Dump Generation
-
-Assuming that the filter callback approves (or does not exist), the handler
-writes a dump in a directory specified by the application developer when the
-handler was installed, using a previously generated unique identifier to avoid
-name collisions. The mechanics of dump generation also vary between platforms,
-but in general, the process involves enumerating each thread of execution, and
-capturing its state, including processor context and the active portion of its
-stack area. The dump also includes a list of the code modules loaded in to the
-application, and an indicator of which thread generated the exception or
-requested the dump. In order to avoid allocating memory during this process, the
-dump is written in place on disk.
-
-### Post-Dump Behavior
-
-Upon completion of writing the dump, a second callback function is called. This
-callback may be used to launch a separate crash reporting program or to collect
-additional data from the application. The callback may also be used to influence
-whether Breakpad will treat the exception as handled or unhandled. Even after a
-dump is successfully generated, Breakpad can be made to behave as though it
-didn’t actually handle an exception. This function may be useful for developers
-who want to test their applications with Breakpad enabled but still retain the
-ability to use traditional debugging techniques. It also allows a
-Breakpad-enabled application to coexist with a platform’s native crash reporting
-system, such as Mac OS X’ [CrashReporter](http://developer.apple.com/technotes/tn2004/tn2123.html)
-and [Windows Error Reporting](http://msdn.microsoft.com/isv/resources/wer/).
-
-Typically, when Breakpad handles an exception fully and no debuggers are
-involved, the crashed process will terminate.
-
-Authors of both callback functions that execute within a Breakpad handler are
-cautioned that their code will be run at exception time, and that as a result,
-they should observe the same programming practices that the Breakpad handler
-itself adheres to. Notably, if a callback is to be used to collect additional
-data from an application, it should take care to read only “safe” data. This
-might involve accessing only static memory locations that are updated
-periodically during the course of normal program execution.
-
-### Sender Library
-
-The Breakpad sender library provides a single function to send a crash report to
-a crash server. It accepts a crash server’s URL, a map of key-value parameters
-that will accompany the dump, and the path to a dump file itself. Each of the
-key-value parameters and the dump file are sent as distinct parts of a multipart
-HTTP POST request to the specified URL using the platform’s native HTTP
-facilities. On Linux, [libcurl](http://curl.haxx.se/) is used for this function,
-as it is the closest thing to a standard HTTP library available on that
-platform.
-
-## Future Plans
-
-Although we’ve had great success with in-process dump generation by following
-our guidelines for safe code at exception time, we are exploring options for
-allowing dumps to be generated in a separate process, to further enhance the
-handler library’s robustness.
-
-On Windows, we intend to offer tools to make it easier for Breakpad’s settings
-to be managed by the native group policy management system.
-
-We also plan to offer tools that many developers would find desirable in the
-context of handling crashes, such as a mechanism to determine at launch if the
-program last terminated in a crash, and a way to calculate “crashiness” in terms
-of crashes over time or the number of application launches between crashes.
-
-We are also investigating methods to capture crashes that occur early in an
-application’s launch sequence, including crashes that occur before a program’s
-main function begins executing.
@@ -1,35 +0,0 @@
-# Introduction
-
-Thanks for thinking of contributing to Breakpad! Unfortunately there are some
-pesky legal issues to get out of the way, but they're quick and painless.
-
-## Legal
-
-If you're doing work individually, not as part of any employment, you'll need to
-sign the <a
-href='http://code.google.com/legal/individual-cla-v1.0.html'>Individual
-Contributor License Agreement</a>. This agreement can be completed
-electronically.
-
-If you're contributing to Breakpad as part of your employment with another
-organization, you'll need to sign a <a
-href='http://code.google.com/legal/corporate-cla-v1.0.html'> Corporate
-Contributor License Agreement</a>. Once completed this document will need to be
-faxed.
-
-**_IMPORTANT_**: The authors(you!) of the contributions will maintain all
-copyrights; the agreements you sign will grant rights to Google to use your
-work.
-
-Thanks, and if you have any questions let me know and I'll loop in the legal guy
-here to get you an answer.
-
-## Technical
-
-Once you have signed the agreement you can be added to our contributors list and
-have write access to code. For full details on getting started see our trunk
-`README`.
-
-## List of people who have signed contributor agreements
-
-None so far.
@@ -1,128 +0,0 @@
-The goal of this document is to give an overview of the exception handling
-options in breakpad.
-
-# Basics
-
-Exception handling is a mechanism designed to handle the occurrence of
-exceptions, special conditions that change the normal flow of program execution.
-
-`SetUnhandledExceptionFilter` replaces all unhandled exceptions when Breakpad is
-enabled. TODO: More on first and second change and vectored v. try/catch.
-
-There are two main types of exceptions across all platforms: in-process and
-out-of-process.
-
-# In-Process
-
-In process exception handling is relatively simple since the crashing process
-handles crash reporting. It is generally considered unsafe to write a minidump
-from a crashed process. For example, key data structures could be corrupted or
-the stack on which the exception handler runs could have been overwritten. For
-this reason all platforms also support some level of out-of-process exception
-handling.
-
-## Windows
-
-In-process exception handling Breakpad creates a 'handler head' that waits
-infinitely on a semaphore at start up. When this thread is woken it writes the
-minidump and signals to the excepting thread that it may continue. A filter will
-tell the OS to kill the process if the minidump is written successfully.
-Otherwise it continues.
-
-# Out-of-Process
-
-Out-of-process exception handling is more complicated than in-process exception
-handling because of the need to set up a separate process that can read the
-state of the crashing process.
-
-## Windows
-
-Breakpad uses two abstractions around the exception handler to make things work:
-`CrashGenerationServer` and `CrashGenerationClient`. The constructor for these
-takes a named pipe name.
-
-During server start up a named pipe and registers callbacks for client
-connections are created. The named pipe is used for registration and all IO on
-the pipe is done asynchronously. `OnPipeConnected` is called when a client
-attempts to connect (call `CreateFile` on the pipe). `OnPipeConnected` does the
-state machine transition from `Initial` to `Connecting` and on through
-`Reading`, `Reading_Done`, `Writing`, `Writing_Done`, `Reading_ACK`, and
-`Disconnecting`.
-
-When registering callbacks, the client passes in two pointers to pointers: 1. A
-pointer to the `EXCEPTION_INFO` pointer 1. A pointer to the `MDRawAssertionInfo`
-which handles various non-exception failures like assertions
-
-The essence of registration is adding a "`ClientInfo`" object that contains
-handles used for synchronization with the crashing process to an array
-maintained by the server. This is how we can keep track of all the clients on
-the system that have registered for minidumps. These handles are: *
-`server_died(mutex)` * `dump_requested(Event)` * `dump_generated(Event)`
-
-The server registers asynchronous waits on these events with the `ClientInfo`
-object as the callback context. When the `dump_requested` event is set by the
-client, the `OnDumpRequested()` callback is called. The server uses the handles
-inside `ClientInfo` to communicate with the child process. Once the child sets
-the event, it waits for two objects: 1. the `dump_generated` event 1. the
-`server_died` mutex
-
-In the end handles are "duped" into the client process, and the clients use
-`SetEvent` to request events, wait on the other event, or the `server_died`
-mutex.
-
-## Linux
-
-### Current Status
-
-As of July 2011, Linux had a minidump generator that is not entirely
-out-of-process. The minidump was generated from a separate process, but one that
-shared an address space, file descriptors, signal handles and much else with the
-crashing process. It worked by using the `clone()` system call to duplicate the
-crashing process, and then uses `ptrace()` and the `/proc` file system to
-retrieve the information required to write the minidump. Since then Breakpad has
-updated Linux exception handling to provide more benefits of out-of-process
-report generation.
-
-### Proposed Design
-
-#### Overview
-
-Breakpad would use a per-user daemon to write out a minidump that does not have,
-interact with or depend on the crashing process. We don't want to start a new
-separate process every time a user launches a Breakpad-enabled process. Doing
-one daemon per machine is unacceptable for security concerns around one user
-being able to initiate a minidump generation for another user's process.
-
-#### Client/Server Communication
-
-On Breakpad initialization in a process, the initializer would check if the
-daemon is running and, if not, start it. The race condition between the check
-and the initialization is not a problem because multiple daemons can check if
-the IPC endpoint already exists and if a server is listening. Even if multiple
-copies of the daemon try to `bind()` the filesystem to name the socket, all but
-one will fail and can terminate.
-
-This point is relevant for error handling conditions. Linux does not clean the
-file system representation of a UNIX domain socket even if both endpoints
-terminate, so checking for existence is not strong enough. However checking the
-process list or sending a ping on the socket can handle this.
-
-Breakpad uses UNIX domain sockets since they support full duplex communication
-(unlike Windows, named pipes on Linux are half) and the kernal automatically
-creates a private channel between the client and server once the client calls
-`connect()`.
-
-#### Minidump Generation
-
-Breakpad could use the current system with `ptrace()` and `/proc` within the
-daemon executable.
-
-Overall the operations look like: 1. Signal from OS indicating crash 1. Signal
-Handler suspends all threads except itself 1. Signal Handler sends
-`CRASH_DUMP_REQUEST` message to server and waits for response 1. Server inspects
-1. Minidump is asynchronously written to disk by the server 1. Server responds
-indicating inspection is done
-
-## Mac OSX
-
-Out-of-process exception handling is fully supported on Mac.
@@ -1,115 +0,0 @@
-# Introduction
-
-Breakpad is a library and tool suite that allows you to distribute an
-application to users with compiler-provided debugging information removed,
-record crashes in compact "minidump" files, send them back to your server, and
-produce C and C++ stack traces from these minidumps. Breakpad can also write
-minidumps on request for programs that have not crashed.
-
-Breakpad is currently used by Google Chrome, Firefox, Google Picasa, Camino,
-Google Earth, and other projects.
-
-![Workflow](breakpad.png)
-
-Breakpad has three main components:
-
-*   The **client** is a library that you include in your application. It can
-    write minidump files capturing the current threads' state and the identities
-    of the currently loaded executable and shared libraries. You can configure
-    the client to write a minidump when a crash occurs, or when explicitly
-    requested.
-
-*   The **symbol dumper** is a program that reads the debugging information
-    produced by the compiler and produces a **symbol file**, in [Breakpad's own
-    format](symbol_files.md).
-
-*   The **processor** is a program that reads a minidump file, finds the
-    appropriate symbol files for the versions of the executables and shared
-    libraries the minidump mentions, and produces a human-readable C/C++ stack
-    trace.
-
-# The minidump file format
-
-The minidump file format is similar to core files but was developed by Microsoft
-for its crash-uploading facility. A minidump file contains:
-
-*   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. These data are uninterpreted byte streams, as the
-    Breakpad client generally has no debugging information available to produce
-    function names or line numbers, or even identify stack frame boundaries.
-
-*   Other information about the system on which the dump was collected:
-    processor and operating system versions, the reason for the dump, and so on.
-
-Breakpad uses Windows minidump files on all platforms, instead of the
-traditional core files, for several reasons:
-
-*   Core files can be very large, making them impractical to send across a
-    network to the collector for processing. Minidumps are smaller, as they were
-    designed to be used this way.
-
-*   The core file format is poorly documented. For example, the Linux Standards
-    Base does not describe how registers are stored in `PT_NOTE` segments.
-
-*   It is harder to persuade a Windows machine to produce a core dump file than
-    it is to persuade other machines to write a minidump file.
-
-*   It simplifies the Breakpad processor to support only one file format.
-
-# Overview/Life of a minidump
-
-A minidump is generated via calls into the Breakpad library. By default,
-initializing Breakpad installs an exception/signal handler that writes a
-minidump to disk at exception time. On Windows, this is done via
-`SetUnhandledExceptionFilter()`; on OS X, this is done by creating a thread that
-waits on the Mach exception port; and on Linux, this is done by installing a
-signal handler for various exceptions like `SIGILL, SIGSEGV` etc.
-
-Once the minidump is generated, each platform has a slightly different way of
-uploading the crash dump. On Windows & Linux, a separate library of functions is
-provided that can be called into to do the upload. On OS X, a separate process
-is spawned that prompts the user for permission, if configured to do so, and
-sends the file.
-
-# Terminology
-
-**In-process vs. out-of-process exception handling** - it's generally considered
-that writing the minidump from within the crashed process is unsafe - key
-process data structures could be corrupted, or the stack on which the exception
-handler runs could have been overwritten, etc. All 3 platforms support what's
-known as "out-of-process" exception handling.
-
-# Integration overview
-
-## Breakpad Code Overview
-
-All the client-side code is found by visiting the Google Project at
-https://chromium.googlesource.com/breakpad/breakpad. The following directory structure is
-present in the `src` directory:
-
-*   `processor` Contains minidump-processing code that is used on the server
-    side and isn't of use on the client side
-*   `client` Contains client minidump-generation libraries for all platforms
-*   `tools` Contains source code & projects for building various tools on each
-    platform.
-
-(Among other directories)
-
-*   [Windows Integration Guide](windows_client_integration.md)
-*   [Mac Integration Guide](mac_breakpad_starter_guide.md)
-*   [Linux Integration Guide](linux_starter_guide.md)
-
-## Build process specifics(symbol generation)
-
-This applies to all platforms. Inside `src/tools/{platform}/dump_syms` is a tool
-that can read debugging information for each platform (e.g. for OS X/Linux,
-DWARF and STABS, and for Windows, PDB files) and generate a Breakpad symbol
-file. This tool should be run on your binary before it's stripped(in the case of
-OS X/Linux) and the symbol files need to be stored somewhere that the minidump
-processor can find. There is another tool, `symupload`, that can be used to
-upload symbol files if you have written a server that can accept them.
@@ -1,39 +0,0 @@
-# How To Use Breakpad As a Coredump Handler on Linux
-
-This document presents a way to use Breakpad in order to generate
-minidumps system wide on Linux.
-
-Please refer to [Linux starter guide](./linux_starter_guide.md) if
-instead you want to integrate breakpad into your application.
-
-## Motivation
-
-When working on an embedded system, disk and memory space is often
-limited and when a process crashes it must be restarted as soon as
-possible. Sometime saving a full coredump takes to much time or
-consumes too much space.
-
-## Breakpad Core Handler
-
-In such case the program `core_handler` can be use to generate
-minidumps instead of coredumps. `core_handler` reads the firsts
-sections of the coredump (where the various threads are described)
-generated by Linux from the standard input and then directly reads
-`/proc/<pid>/mem` to reconstruct the stacktraces.
-
-One can test it with:
-
-```
-# echo "|/usr/libexec/core_handler %P /var/lib/minidump/%e-%i.md" >
-                /proc/sys/kernel/core_pattern
-# echo 1 > /proc/sys/kernel/core_pipe_limit
-```
-
-Be aware that a real world integration would likely require further
-customization and so `core_handler` can be wrapped into a script (for
-example to change the permission of the minidump file or to signal the
-presence of the minidump to another service).
-
-Please refer to
-[core(5)](https://man7.org/linux/man-pages/man5/core.5.html) for more
-details.
@@ -1,110 +0,0 @@
-# How To Add Breakpad To Your Linux Application
-
-This document is an overview of using the Breakpad client libraries on Linux.
-
-## Building the Breakpad libraries
-
-Breakpad provides an Autotools build system that will build both the Linux
-client libraries and the processor libraries. Running `./configure && make` in
-the Breakpad source directory will produce
-**src/client/linux/libbreakpad\_client.a**, which contains all the code
-necessary to produce minidumps from an application.
-
-## Integrating Breakpad into your Application
-
-First, configure your build process to link **libbreakpad\_client.a** into your
-binary, and set your include paths to include the **src** directory in the
-**google-breakpad** source tree. Next, include the exception handler header:
-
-```cpp
-#include "client/linux/handler/exception_handler.h"
-```
-
-Now you can instantiate an `ExceptionHandler` object. Exception handling is active for the lifetime of the `ExceptionHandler` object, so you should instantiate it as early as possible in your application's startup process, and keep it alive for as close to shutdown as possible. To do anything useful, the `ExceptionHandler` constructor requires a path where it can write minidumps, as well as a callback function to receive information about minidumps that were written:
-
-```cpp
-static bool dumpCallback(const google_breakpad::MinidumpDescriptor& descriptor,
-void* context, bool succeeded) {
-  printf("Dump path: %s\n", descriptor.path());
-  return succeeded;
-}
-
-void crash() { volatile int* a = (int*)(NULL); *a = 1; }
-
-int main(int argc, char* argv[]) {
-  google_breakpad::MinidumpDescriptor descriptor("/tmp");
-  google_breakpad::ExceptionHandler eh(descriptor, NULL, dumpCallback, NULL, true, -1);
-  crash();
-  return 0;
-}
-```
-
-Compiling and running this example should produce a minidump file in /tmp, and
-it should print the minidump filename before exiting. You can read more about
-the other parameters to the `ExceptionHandler` constructor [in the exception_handler.h source file][1].
-
-[1]: https://chromium.googlesource.com/breakpad/breakpad/+/master/src/client/linux/handler/exception_handler.h
-
-**Note**: You should do as little work as possible in the callback function.
-Your application is in an unsafe state. It may not be safe to allocate memory or
-call functions from other shared libraries. The safest thing to do is `fork` and
-`exec` a new process to do any work you need to do. If you must do some work in
-the callback, the Breakpad source contains [some simple reimplementations of libc functions][2], to avoid calling directly into
-libc, as well as [a header file for making Linux system calls][3] (in **src/third\_party/lss**) to avoid calling into other shared libraries.
-
-[2]: https://chromium.googlesource.com/breakpad/breakpad/+/master/src/common/linux/linux_libc_support.h
-[3]: https://chromium.googlesource.com/linux-syscall-support/+/master
-
-## Sending the minidump file
-
-In a real application, you would want to handle the minidump in some way, likely
-by sending it to a server for analysis. The Breakpad source tree contains [some
-HTTP upload source][4] that you might find useful, as well as [a minidump upload tool][5].
-
-[4]: https://chromium.googlesource.com/breakpad/breakpad/+/master/src/common/linux/http_upload.h
-[5]: https://chromium.googlesource.com/breakpad/breakpad/+/master/src/tools/linux/symupload/minidump_upload.cc
-
-## Producing symbols for your application
-
-To produce useful stack traces, Breakpad requires you to convert the debugging
-symbols in your binaries to [text-format symbol files][6]. First, ensure that you've compiled your binaries with `-g` to
-include debugging symbols. Next, compile the `dump_syms` tool by running
-`configure && make` in the Breakpad source directory. Next, run `dump_syms` on
-your binaries to produce the text-format symbols. For example, if your main
-binary was named `test`:
-
-[6]: https://chromium.googlesource.com/breakpad/breakpad/+/master/docs/symbol_files.md
-
-```
-$ google-breakpad/src/tools/linux/dump_syms/dump_syms ./test > test.sym
-```
-
-In order to use these symbols with the `minidump_stackwalk` tool, you will need
-to place them in a specific directory structure. The first line of the symbol
-file contains the information you need to produce this directory structure, for
-example (your output will vary):
-
-```
-$ head -n1 test.sym MODULE Linux x86_64 6EDC6ACDB282125843FD59DA9C81BD830 test
-$ mkdir -p ./symbols/test/6EDC6ACDB282125843FD59DA9C81BD830
-$ mv test.sym ./symbols/test/6EDC6ACDB282125843FD59DA9C81BD830
-```
-
-You may also find the [symbolstore.py][7] script in the Mozilla repository useful, as it encapsulates these steps.
-
-[7]: https://dxr.mozilla.org/mozilla-central/source/toolkit/crashreporter/tools/symbolstore.py
-
-## Processing the minidump to produce a stack trace
-
-Breakpad includes a tool called `minidump_stackwalk` which can take a minidump
-plus its corresponding text-format symbols and produce a symbolized stacktrace.
-It should be in the **google-breakpad/src/processor** directory if you compiled
-the Breakpad source using the directions above. Simply pass it the minidump and
-the symbol path as commandline parameters:
-
-```
-$ google-breakpad/src/processor/minidump_stackwalk minidump.dmp ./symbols
-```
-
-It produces verbose output on stderr, and the stacktrace on stdout, so you may
-want to redirect stderr.
@@ -1,47 +0,0 @@
-# Introduction
-
-Linux implements its userland-to-kernel transition using a special library
-called linux-gate.so that is mapped by the kernel into every process. For more
-information, see
-
-http://www.trilithium.com/johan/2005/08/linux-gate/
-
-In a nutshell, the problem is that the system call gate function,
-kernel\_vsyscall does not use EBP to point to the frame pointer.
-
-However, the Breakpad processor supports special frames like this via STACK
-lines in the symbol file. If you look in src/client/linux/data you will see
-symbol files for linux-gate.so for both Intel & AMD(the implementation of
-kernel\_vsyscall changes depending on the CPU manufacturer). When processing
-minidumps from Linux 2.6, having these symbol files is necessary for walking the
-stack for crashes that happen while a thread is in a system call.
-
-If you're just interested in processing minidumps, those two symbol files should
-be all you need!
-
-# Details
-
-The particular details of understanding the linux-gate.so symbol files can be
-found by reading about STACK lines inside
-src/common/windows/pdb\_source\_line\_writer.cc, and the above link. To
-summarize briefly, we just have to inform the processor how to get to the
-previous frame when the EIP is inside kernel\_vsyscall, and we do that by
-telling the processor how many bytes kernel\_vsyscall has pushed onto the stack
-in it's prologue. For example, one of the symbol files looks somewhat like the
-following:
-
-MODULE Linux x86 random\_debug\_id linux-gate.so PUBLIC 400 0 kernel\_vsyscall
-STACK WIN 4 100 1 1 0 0 0 0 0 1
-
-The PUBLIC line indicates that kernel\_vsyscall is at offset 400 (in bytes) from
-the beginning of linux-gate.so. The STACK line indicates the size of the
-function(100), how many bytes it pushes(1), and how many bytes it pops(1). The
-last 1 indicates that EBP is pushed onto the stack before being used by the
-function.
-
-# Warnings
-
-These functions might change significantly depending on kernel version. In my
-opinion, the actual function stack information is unlikely to change frequently,
-but the Linux kernel might change the address of kernel\_vsyscall w.r.t the
-beginning of linux-gate.so, which would cause these symbol files to be invalid.
@@ -1,184 +0,0 @@
-# How To Add Breakpad To Your Mac Client Application
-
-This document is a step-by-step recipe to get your Mac client app to build with
-Breakpad.
-
-## Preparing a binary build of Breakpad for use in your tree
-
-You can either check in a binary build of the Breakpad framework & tools or
-build it as a dependency of your project. The former is recommended, and
-detailed here, since building dependencies through other projects is
-problematic(matching up configuration names), and the Breakpad code doesn't
-change nearly often enough as your application's will.
-
-## Building the requisite targets
-
-All directories are relative to the `src` directory of the Breakpad checkout.
-
-*   Build the 'All' target of `client/mac/Breakpad.xcodeproj` in Release mode.
-*   Execute `cp -R client/mac/build/Release/Breakpad.framework <location in your
-    source tree>`
-*   Inside `tools/mac/dump_syms` directory, build dump\_syms.xcodeproj, and copy
-    tools/mac/dump\_syms/build/Release/dump\_syms to a safe location where it
-    can be run during the build process.
-
-## Adding Breakpad.framework
-
-Inside your application's framework, add the Breakpad.Framework to your
-project's framework settings. When you select it from the file chooser, it will
-let you pick a target to add it to; go ahead and check the one that's relevant
-to your application.
-
-## Copy Breakpad into your Application Package
-
-Copy Breakpad into your Application Package, so it will be around at run time.
-
-Go to the Targets section of your Xcode Project window. Hit the disclosure
-triangle to reveal the build phases of your application. Add a new Copy Files
-phase using the Contextual menu (Control Click). On the General panel of the new
-'Get Info' of this new phase, set the destination to 'Frameworks' Close the
-'Info' panel. Use the Contextual Menu to Rename your new phase 'Copy Frameworks'
-Now drag Breakpad again into this Copy Frameworks phase. Drag it from whereever
-it appears in the project file tree.
-
-## Add a New Run Script build phase
-
-Near the end of the build phases, add a new Run Script build phase. This will be
-run before Xcode calls /usr/bin/strip on your project. This is where you'll be
-calling dump\_sym to output the symbols for each architecture of your build. In
-my case, the relevant lines read:
-
-```
-#!/bin/sh
-$TOOL_DIR=<location of dump_syms from step 3 above>
-
-"$TOOL_DIR/dump_syms" -a ppc "$PROD" > "$TARGET_NAME ppc.breakpad"
-
-"$TOOL_DIR/dump_syms" -a i386 "$PROD" > "$TARGET_NAME i386.breakpad"
-```
-
-## Adjust the Project Settings
-
-*   Turn on Separate Strip,
-*   Set the Strip Style to Non-Global Symbols.
-
-## Write Code!
-
-You'll need to have an object that acts as the delegate for NSApplication.
-Inside this object's header, you'll need to add
-
-1.  add an ivar for Breakpad and
-2.  a declaration for the applicationShouldTerminate:(NSApplication`*` sender)
-    message.
-
-```
-#import <Breakpad/Breakpad.h>
-
-@interface BreakpadTest : NSObject {
-   .
-   .
-   .
-   BreakpadRef breakpad;
-   .
-   .
-   .
-}
-.
-.
- (NSApplicationTerminateReply)applicationShouldTerminate:(NSApplication *)sender;
-.
-.
-@end
-```
-
-Inside your object's implementation file,
-
-1.  add the following method InitBreakpad
-2.  modify your awakeFromNib method to look like the one below,
-3.  modify/add your application's delegate method to look like the one below
-
-```
-static BreakpadRef InitBreakpad(void) {
-  NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
-  BreakpadRef breakpad = 0;
-  NSDictionary *plist = [[NSBundle mainBundle] infoDictionary];
-  if (plist) {
-    // Note: version 1.0.0.4 of the framework changed the type of the argument 
-    // from CFDictionaryRef to NSDictionary * on the next line:
-    breakpad = BreakpadCreate(plist);
-  }
-  [pool release];
-  return breakpad;
-}
-
- (void)awakeFromNib {
-  breakpad = InitBreakpad();
-}
-
- (NSApplicationTerminateReply)applicationShouldTerminate:(NSApplication *)sender {
-  BreakpadRelease(breakpad);
-  return NSTerminateNow;
-}
-```
-
-## Configure Breakpad
-
-Configure Breakpad for your application.
-
-1.  Take a look inside the Breakpad.framework at the Breakpad.h file for the
-    keys, default values, and descriptions to be passed to BreakpadCreate().
-2.  Add/Edit the Breakpad specific entries in the dictionary passed to
-    BreakpadCreate() -- typically your application's info plist.
-
-Example from the Notifier Info.plist:
-`<key>BreakpadProduct</key><string>Google_Notifier_Mac</string>
-<key>BreakpadProductDisplay</key><string>${PRODUCT_NAME}</string>
-`
-
-## Build Your Application
-
-Almost done!
-
-## Verify
-
-Double-check:
-
-Your app should have in its package contents:
-myApp.app/Contents/Frameworks/Breakpad.framework.
-
-The symbol files have reasonable contents (you can look at them with a text
-editor.)
-
-Look again at the Copy Frameworks phase of your project. Are you leaking .h
-files? Select them and delete them. (If you drag a bunch of files into your
-project, Xcode often wants to copy your .h files into the build, revealing
-Google secrets. Be vigilant!)
-
-## Upload the symbol file
-
-You'll need to configure your build process to store symbols in a location that
-is accessible by the minidump processor. There is a tool in tools/mac/symupload
-that can be used to send the symbol file via HTTP post.
-
-1.  Test
-
-Configure breakpad to send reports to a URL by adding to your app's Info.plist:
-
-```
-<key>BreakpadURL</key>
-<string>upload URL</string>
-<key>BreakpadReportInterval</key>
-<string>30</string>
-```
-
-## Final Notes
-
-Breakpad checks whether it is being run under a debugger, and if so, normally
-does nothing. But, you can force Breakpad to function under a debugger by
-setting the Unix shell variable BREAKPAD\_IGNORE\_DEBUGGER to a non-zero value.
-You can bracket the source code in the above Write The Code step with #if DEBUG
-to completely eliminate it from Debug builds. See
-//depot/googlemac/GoogleNotifier/main.m for an example. FYI, when your process
-forks(), exception handlers are reset to the default for child processes. So
-they must reinitialize Breakpad, otherwise exceptions will be handled by Apple's
-Crash Reporter.
@@ -1,82 +0,0 @@
-# Breakpad Crash Reporting for Mozilla
-
-*   January 24, 2007
-    *   Links updated February 14, 2007
-*   Mozilla HQ
-*   Mark Mentovai
-*   Brian Ryner
-
-## What is a crash reporter?
-
-*   Enables developers to analyze crashes that occur in the wild
-*   Produces stack backtraces that help identify how a program failed
-*   Offers higher-level data aggregation (topcrashes, MTBF statistics)
-
-## Motivation
-
-*   Talkback is proprietary and unmaintained
-*   Smaller open-source projects have few options
-*   Larger projects need flexibility and scalability
-
-## Design Options
-
-*   Stackwalking done on client
-    *   Apple CrashReporter
-    *   GNOME BugBuddy
-*   Client sends memory dump
-    *   Talkback
-    *   Windows Error Reporting
-    *   Breakpad
-
-## Goals
-
-*   Provide libraries around which systems can be based
-*   Open-source
-*   Cross-platform
-    *   Mac OS X x86, PowerPC
-    *   Linux x86
-    *   Windows x86
-*   No requirement to distribute symbols
-
-## Client Libraries
-
-*   Exception handler installed at application startup
-    *   Spawns a separate thread
-*   Minidump file written at crash time
-    *   Format used by Windows debuggers
-*   Separate application invoked to send
-    *   HTTP[S](S.md) POST, can include additional parameters
-
-## Symbols
-
-*   Cross-platform symbol file format
-*   Contents
-    *   Function names
-    *   Source file names and line numbers
-    *   Windows: Frame pointer omission data
-    *   Future: parameters and local variables
-*   Symbol conversion methods
-
-## Processor
-
-*   Examines minidump file and invokes stackwalker
-*   Symbol files requested from a SymbolSupplier
-*   Produces stack trace
-*   Output may be placed where convenient
-
-## Intergation
-
-*   Breakpad client present in Gran Paradiso Alpha 1 for Windows
-    *   Disabled by default
-    *   Enable with `MOZ_AIRBAG`
-*   Proof-of-concept collector
-    *   http://mavra.perilith.com/~luser/airbag-collector/list.pl
-*   Other platforms coming soon
-
-## More Information
-
-*   Project home: https://chromium.googlesource.com/breakpad/breakpad
-*   Mailing lists
-    *   [[email protected]](http://groups.google.com/group/google-breakpad-dev/)
-    *   [[email protected]](http://groups.google.com/group/google-breakpad-discuss/)
-*   Ask me (irc.mozilla.org: mento)
@@ -1,231 +0,0 @@
-# Breakpad Processor Library
-
-## Objective
-
-The Breakpad processor library is an open-source framework to access the the
-information contained within crash dumps for multiple platforms, and to use that
-information to produce stack traces showing the call chain of each thread in a
-process. After processing, this data is made available to users of the library.
-
-## Background
-
-The Breakpad processor is intended to sit at the core of a comprehensive
-crash-reporting system that does not require debugging information to be
-provided to those running applications being monitored. Some existing
-crash-reporting systems, such as [GNOME](http://www.gnome.org/)’s Bug-Buddy and
-[Apple](http://www.apple.com/)’s
-[CrashReporter](http://developer.apple.com/technotes/tn2004/tn2123.html),
-require symbolic
-information to be present on the end user’s computer; in the case of
-CrashReporter, the reports are transmitted only to Apple, not to third-party
-developers. Other systems, such as [Microsoft](http://www.microsoft.com/)’s
-[Windows Error Reporting](http://msdn.microsoft.com/isv/resources/wer/) and
-SupportSoft’s Talkback, transmit only a snapshot of a crashed process’ state,
-which can later be combined with symbolic debugging information without the need
-for it to be present on end users’ computers. Because symbolic debugging
-information consumes a large amount of space and is otherwise not needed during
-the normal operation of software, and because some developers are reluctant to
-release debugging symbols to their customers, Breakpad follows the latter
-approach.
-
-We know of no currently-maintained crash-reporting systems that meet our
-requirements, which are to: * allow for symbols to be separate from the
-application, * handle crash reports from multiple platforms, * allow developers
-to operate their own crash-reporting platform, and to * be open-source. Windows
-Error Reporting only functions for Microsoft products, and requires the
-involvement of Microsoft’s servers. Talkback, while cross-platform, has not been
-maintained and at this point does not support Mac OS X on x86, which we consider
-to be a significant platform. Talkback is also closed-source commercial
-software, and has very specific requirements for its server platform.
-
-We are aware of Windows-only crash-reporting systems that leverage Microsoft’s
-debugging interfaces. Such systems, even if extended to support dumps from other
-platforms, are tied to using Windows for at least a portion of the processor
-platform.
-
-## Overview
-
-The Breakpad processor itself is written in standard C++ and will work on a
-variety of platforms. The dumps it accepts may also have been created on a
-variety of systems. The library is able to combine dumps with symbolic debugging
-information to create stack traces that include function signatures. The
-processor library includes simple command-line tools to examine dumps and
-process them, producing stack traces. It also exposes several layers of APIs
-enabling crash-reporting systems to be built around the Breakpad processor.
-
-## Detailed Design
-
-### Dump Files
-
-In the processor, the dump data is of primary significance. Dumps typically
-contain:
-
-*   CPU context (register data) as it was at the time the crash occurred, and an
-    indication of which thread caused the crash. General-purpose registers are
-    included, as are special-purpose registers such as the instruction pointer
-    (program counter).
-*   Information about each thread of execution within a crashed process,
-    including:
-    *   The memory region used for each thread’s stack.
-    *   CPU context for each thread, which for various reasons is not the same
-        as the crash context in the case of the crashed thread.
-*   A list of loaded code segments (or modules), including:
-    *   The name of the file (`.so`, `.exe`, `.dll`, etc.) which provides the
-        code.
-    *   The boundaries of the memory region in which the code segment is visible
-        to the process.
-    *   A reference to the debugging information for the code module, when such
-        information is available.
-
-Ordinarily, dumps are produced as a result of a crash, but other triggers may be
-set to produce dumps at any time a developer deems appropriate. The Breakpad
-processor can handle dumps in the minidump format, either generated by an
-[Breakpad client “handler”](client_design.md) implementation, or by another
-implementation that produces dumps in this format. The
-[DbgHelp.dll!MiniDumpWriteDump](http://msdn2.microsoft.com/en-us/library/ms680360.aspx)
-function on Windows
-produces dumps in this format, and is the basis for the Breakpad handler
-implementation on that platform.
-
-The [minidump format](http://msdn.microsoft.com/en-us/library/ms679293%28VS.85%29.aspx) is
-essentially a simple container format, organized as a series of streams. Each
-stream contains some type of data relevant to the crash. A typical “normal”
-minidump contains streams for the thread list, the module list, the CPU context
-at the time of the crash, and various bits of additional system information.
-Other types of minidump can be generated, such as a full-memory minidump, which
-in addition to stack memory contains snapshots of all of a process’ mapped
-memory regions.
-
-The minidump format was chosen as Breakpad’s dump format because it has an
-established track record on Windows, and it can be adapted to meet the needs of
-the other platforms that Breakpad supports. Most other operating systems use
-“core” files as their native dump formats, but the capabilities of core files
-vary across platforms, and because core files are usually presented in a
-platform’s native executable format, there are complications involved in
-accessing the data contained therein without the benefit of the header files
-that define an executable format’s entire structure. Because minidumps are
-leaner than a typical executable format, a redefinition of the format in a
-cross-platform header file, `minidump_format.h`, was a straightforward task.
-Similarly, the capabilities of the minidump format are understood, and because
-it provides an extensible container, any of Breakpad’s needs that could not be
-met directly by the standard minidump format could likely be met by extending it
-as needed. Finally, using this format means that the dump file is compatible
-with native debugging tools at least on Windows. A possible future avenue for
-exploration is the conversion of minidumps to core files, to enable this same
-benefit on other platforms.
-
-We have already provided an extension to the minidump format that allows it to
-carry dumps generated on systems with PowerPC processors. The format already
-allows for variable CPUs, so our work in this area was limited to defining a
-context structure sufficient to represent the execution state of a PowerPC. We
-have also defined an extension that allows minidumps to indicate which thread of
-execution requested a dump be produced for non-crash dumps.
-
-Often, the information contained within a dump alone is sufficient to produce a
-full stack backtrace for each thread. Certain optimizations that compilers
-employ in producing code frustrate this process. Specifically, the “frame
-pointer omission” optimization of x86 compilers can make it impossible to
-produce useful stack traces given only a stack snapshot and CPU context. In
-these cases, however, compiler-emitted debugging information can aid in
-producing useful stack traces. The Breakpad processor is able to take advantage
-of this debugging information as supplied by Microsoft’s C/C++ compiler, the
-only compiler to apply such optimizations by default. As a result, the Breakpad
-processor can produce useful stack traces even from code with frame pointer
-omission optimizations as produced by this compiler.
-
-### Symbol Files
-
-The [symbol files](symbol_files.md) that the Breakpad processor accepts allow
-for frame pointer omission data, but this is only one of their capabilities.
-Each symbol file also includes information about the functions, source files,
-and source code line numbers for a single module of code. A module is an
-individually-loadble chunk of code: these can be executables containing a main
-program (`exe` files on Windows) or shared libraries (`.so` files on Linux,
-`.dylib` files, frameworks, and bundles on Mac OS X, and `.dll` files on
-Windows). Dumps contain information about which of these modules were loaded at
-the time the dump was produced, and given this information, the Breakpad
-processor attempts to locate debugging symbols for the module through a
-user-supplied function embodied in a “symbol supplier.” Breakpad includes a
-sample symbol supplier, called `SimpleSymbolSupplier`, that is used by its
-command-line tools; this supplier locates symbol files by pathname.
-`SimpleSymbolSupplier` is also available to other users of the Breakpad
-processor library. This allows for the use of a simple reference implementation,
-but preserves flexibility for users who may have more demanding symbol file
-storage needs.
-
-Breakpad’s symbol file format is text-based, and was defined to be fairly
-human-readable and to encompass the needs of multiple platforms. The Breakpad
-processor itself does not operate directly with native symbol formats
-([DWARF](http://dwarf.freestandards.org/) and
-[STABS](http://sourceware.org/gdb/current/onlinedocs/stabs.html)
-on most Unix-like systems,
-[.pdb files](http://msdn2.microsoft.com/en-us/library/yd4f8bd1(VS.80).aspx)
-on Windows),
-because of the complications in accessing potentially complex symbol formats
-with slight variations between platforms, stored within different types of
-binary formats. In the case of `.pdb` files, the debugging format is not even
-documented. Instead, Breakpad’s symbol files are produced on each platform,
-using specific debugging APIs where available, to convert native symbols to
-Breakpad’s cross-platform format.
-
-### Processing
-
-Most commonly, a developer will enable an application to use Breakpad by
-building it with a platform-specific [client “handler”](client_design.md)
-library. After building the application, the developer will create symbol files
-for Breakpad’s use using the included `dump_syms` or `symupload` tools, or
-another suitable tool, and place the symbol files where the processor’s symbol
-supplier will be able to locate them.
-
-When a dump file is given to the processor’s `MinidumpProcessor` class, it will
-read it using its included minidump reader, contained in the `Minidump` family
-of classes. It will collect information about the operating system and CPU that
-produced the dump, and determine whether the dump was produced as a result of a
-crash or at the direct request of the application itself. It then loops over all
-of the threads in a process, attempting to walk the stack associated with each
-thread. This process is achieved by the processor’s `Stackwalker` components, of
-which there are a slightly different implementations for each CPU type that the
-processor is able to handle dumps from. Beginning with a thread’s context, and
-possibly using debugging data, the stackwalker produces a list of stack frames,
-containing each instruction executed in the chain. These instructions are
-matched up with the modules that contributed them to a process, and the
-`SymbolSupplier` is invoked to locate a symbol file. The symbol file is given to
-a `SourceLineResolver`, which matches the instruction up with a specific
-function name, source file, and line number, resulting in a representation of a
-stack frame that can easily be used to identify which code was executing.
-
-The results of processing are made available in a `ProcessState` object, which
-contains a vector of threads, each containing a vector of stack frames.
-
-For small-scale use of the Breakpad processor, and for testing and debugging,
-the `minidump_stackwalk` tool is provided. It invokes the processor and displays
-the full results of processing, optionally allowing symbols to be provided to
-the processor by a pathname-based symbol supplier, `SimpleSymbolSupplier`.
-
-For lower-level testing and debugging, the processor library also includes a
-`minidump_dump` tool, which walks through an entire minidump file and displays
-its contents in somewhat readable form.
-
-### Platform Support
-
-The Breakpad processor library is able to process dumps produced on Mac OS X
-systems running on x86, x86-64, and PowerPC processors, on Windows and Linux
-systems running on x86 or x86-64 processors, and on Android systems running ARM
-or x86 processors. The processor library itself is written in standard C++, and
-should function properly in most Unix-like environments. It has been tested on
-Linux and Mac OS X.
-
-## Future Plans
-
-There are currently no firm plans or timetables to implement any of these
-features, although they are possible avenues for future exploration.
-
-The symbol file format can be extended to carry information about the locations
-of parameters and local variables as stored in stack frames and registers, and
-the processor can use this information to provide enhanced stack traces showing
-function arguments and variable values.
-
-On Mac OS X and Linux, we can provide tools to convert files from the minidump
-format into the native core format. This will enable developers to open dump
-files in a native debugger, just as they are presently able to do with minidumps
-on Windows.
@@ -1,144 +0,0 @@
-# Introduction
-
-This page aims to provide a detailed description of how Breakpad produces stack
-traces from the information contained within a minidump file.
-
-# Details
-
-## Starting the Process
-
-Typically the stack walking process is initiated by instantiating the
-[MinidumpProcessor](../src/processor/minidump_processor.cc)
-class and calling the [MinidumpProcessor::Process](../src/processor/minidump_processor.cc#61)
-method, providing it a minidump file to process. To produce a useful stack
-trace, the MinidumpProcessor requires two other objects which are passed in its
-constructor: a [SymbolSupplier](../src/google_breakpad/processor/symbol_supplier.h)
-and a [SourceLineResolverInterface](../src/google_breakpad/processor/source_line_resolver_interface.h).
-The SymbolSupplier object is responsible for locating and providing SymbolFiles
-that match modules from the minidump. The SourceLineResolverInterface is
-responsible for loading the symbol files and using the information contained
-within to provide function and source information for stack frames, as well as
-information on how to unwind from a stack frame to its caller. More detail will
-be provided on these interactions later.
-
-A number of data streams are extracted from the minidump to begin stack walking:
-the list of threads from the process
-([MinidumpThreadList](../src/google_breakpad/processor/minidump.h#335)),
-the list of modules loaded in the process
-([MinidumpModuleList](../src/google_breakpad/processor/minidump.h#501)),
-and information about the exception that caused the process to crash
-([MinidumpException](../src/google_breakpad/processor/minidump.h#615)).
-
-## Enumerating Threads
-
-For each thread in the thread list
-([MinidumpThread](../src/google_breakpad/processor/minidump.h#299)),
-the thread memory containing the stack for the thread
-([MinidumpMemoryRegion](../src/google_breakpad/processor/minidump.h#236))
-and the CPU context representing the CPU state of the thread at the time the
-dump was written ([MinidumpContext](../src/google_breakpad/processor/minidump.h#171))
-are extracted from the minidump. If the thread being processed is the thread
-that produced the exception then a CPU context is obtained from the
-MinidumpException object instead, which represents the CPU state of the thread
-at the point of the exception. A stack walker is then instantiated by calling
-the [Stackwalker::StackwalkerForCPU](../src/google_breakpad/processor/stackwalker.h#77)
-method and passing it the CPU context, the thread memory, the module list, as
-well as the SymbolSupplier and SourceLineResolverInterface. This method selects
-the specific !Stackwalker subclass based on the CPU architecture of the provided
-CPU context and returns an instance of that subclass.
-
-## Walking a thread's stack
-
-Once a !Stackwalker instance has been obtained, the processor calls the
-[Stackwalker::Walk](../src/google_breakpad/processor/source_line_resolver_interface.h)
-method to obtain a list of frames representing the stack of this thread. The
-!Stackwalker starts by calling the GetContextFrame method which returns a
-StackFrame representing the top of the stack, with CPU state provided by the
-initial CPU context. From there, the stack walker repeats the following steps
-for each frame in turn:
-
-### Finding the Module
-
-The address of the instruction pointer of the current frame is used to determine
-which module contains the current frame by calling the module list's
-[GetModuleForAddress](../src/google_breakpad/processor/code_modules.h#56) method.
-
-### Locating Symbols
-
-If a module is located, the SymbolSupplier is asked to locate symbols
-corresponding to the module by calling its
-[GetCStringSymbolData](../src/google_breakpad/processor/symbol_supplier.h#87)
-method. Typically this is implemented by using the module's debug filename (the
-PDB filename for Windows dumps) and debug identifier (a GUID plus one extra
-digit) as a lookup key. The [SimpleSymbolSupplier](../src/processor/simple_symbol_supplier.cc)
-class simply uses these as parts of a file path to locate a flat file on disk.
-
-### Loading Symbols
-
-If a symbol file is located, the SourceLineResolverInterface is then asked to
-load the symbol file by calling its
-[LoadModuleUsingMemoryBuffer](../src/google_breakpad/processor/source_line_resolver_interface.h#71)
-method. The [BasicSourceLineResolver](../src/processor/basic_source_line_resolver.cc)
-implementation parses the text-format [symbol file](symbol_files.md) into
-in-memory data structures to make lookups by address of function names, source
-line information, and unwind information easy.
-
-### Getting source line information
-
-If a symbol file has been successfully loaded, the SourceLineResolverInterface's
-[FillSourceLineInfo](../src/google_breakpad/processor/source_line_resolver_interface.h#89)
-method is called to provide a function name and source line information for the
-current frame. This is done by subtracting the base address of the module
-containing the current frame from the instruction pointer of the current frame
-to obtain a relative virtual address (RVA), which is a code offset relative to
-the start of the module. This RVA is then used as a lookup into a table of
-functions ([FUNC lines](SymbolFiles#FUNC_records.md) from the symbol file), each
-of which has an associated address range (function start address, function
-size). If a function is found whose address range contains the RVA, then its
-name is used. The RVA is then used as a lookup into a table of source lines
-([line records](SymbolFiles#Line_records.md) from the symbol file), each of
-which also has an associated address range. If a match is found it will provide
-the file name and source line associated with the current frame. If no match was
-found in the function table, another table of publicly exported symbols may be
-consulted ([PUBLIC lines](SymbolFiles#PUBLIC_records.md) from the symbol file).
-Public symbols contain only a start address, so the lookup simply looks for the
-nearest symbol that is less than the provided RVA.
-
-### Finding the caller frame
-
-To find the next frame in the stack, the !Stackwalker calls its
-[GetCallerFrame](../src/google_breakpad/processor/stackwalker.h#186)
-method, passing in the current frame. Each !Stackwalker subclass implements
-GetCallerFrame differently, but there are common patterns.
-
-Typically the first step is to query the SourceLineResolverInterface for the
-presence of detailed unwind information. This is done using its
-[FindWindowsFrameInfo](../src/google_breakpad/processor/source_line_resolver_interface.h#96)
-and [FindCFIFrameInfo](../src/google_breakpad/processor/source_line_resolver_interface.h#102)
-methods. These methods look for Windows unwind info extracted from a PDB file
-([STACK WIN](SymbolFiles#STACK_WIN_records.md) lines from the symbol file), or
-DWARF CFI extracted from a binary ([STACK CFI](SymbolFiles#STACK_CFI_records.md)
-lines from the symbol file) respectively. The information covers address ranges,
-so the RVA of the current frame is used for lookup as with function and source
-line information.
-
-If unwind info is found it provides a set of rules to recover the register state
-of the caller frame given the current register state as well as the thread's
-stack memory. The rules are evaluated to produce the caller frame.
-
-If unwind info is not found then the !Stackwalker may resort to other methods.
-Typically on architectures which specify a frame pointer unwinding by
-dereferencing the frame pointer is tried next. If that is successful it is used
-to produce the caller frame.
-
-If no caller frame was found by any other method most !Stackwalker
-implementations resort to stack scanning by looking at each word on the stack
-down to a fixed depth (implemented in the
-[Stackwalker::ScanForReturnAddress](../src/google_breakpad/processor/stackwalker.h#131)
-method) and using a heuristic to attempt to find a reasonable return address
-(implemented in the
-[Stackwalker::InstructionAddressSeemsValid](../src/google_breakpad/processor/stackwalker.h#111) method).
-
-If no caller frame is found or the caller frame seems invalid, stack walking
-stops. If a caller frame was found then these steps repeat using the new frame
-as the current frame.
@@ -1,214 +0,0 @@
-# Introduction
-
-The `sym_upload` tool is able to operate in `sym-upload-v2` protocol mode, in
-addition to the legacy protocol (which will be referred to as `sym-upload-v1`
-for the rest of this document). For now `sym-upload-v2` is HTTP/REST-based but
-it could be extended to operate over gRPC instead, in the future.
-
-# Table of Contents
-* [Why](#why)
-* [How](#how)
-   * [Uploading](#uploading)
-     * [Uploading with `sym_upload`](#uploading-with-sym_upload)
-     * [Uploading with curl](#uploading-with-curl)
-     * [Serving the `sym-upload-v2` protocol](#serving-the-sym-upload-v2-protocol)
-       * [Authenticate using `key`](#authenticate-using-key)
-       * [Symbol `checkStatus`](#symbol-checkstatus)
-       * [Upload `create`](#upload-create)
-       * [Uploading the symbol file](#uploading-the-symbol-file)
-       * [Upload complete](#upload-complete)
-
-
-# Why
-
-Using `sym_upload` in `sym-upload-v2` protocol mode has the following features
-beyond `sym-upload-v1`:
-  * Authentication via `key` (arbitrary secret).
-  * Symbol identifier (product of `debug_file` and `debug_id`, as recorded in
-output from `dump_syms`) can be checked against existing symbol information on
-server. If it's present, then the upload is skipped entirely.
-
-# How
-
-## Uploading
-
-### Uploading with `sym_upload`
-
-Uploading in `sym-upload-v2` protocol mode is easy. Invoke `sym_upload` like
-```
-$ ./sym_upload -p sym-upload-v2 [-k <API-key>] <symbol-file> <API-URL>
-```
-
-Where `symbol-file` is a symbol file created by `dump_syms`, `API-URL` is the
-URL of your `sym-upload-v2` API service (see next section for details), and
-`API-key` is a secret known to your uploader and server.
-
-For more options see `sym_upload --help`.
-
-### Uploading with curl
-
-As an example, if:
-  * Your API's URL was "https://sym-upload-api".
-  * Your service has assigned you `key` "myfancysecret123".
-  * You wanted to upload the symbol file at "path/to/file_name", with
-`debug_file` being "file_name" and `debug_id` being
-"123123123123123123123123123". Normally you would read these values from
-"path/to/file_name", which in turn was generated by `dump_syms`.
-
-Then you might run:
-```
-$ curl https://sym-upload-api/symbols/file_name/123123123123123123123123123:checkStatus?key=myfancysecret123
-```
-
-And, upon seeing that this `debug_file`/`debug_id` combo is missing from symbol
-storage then you could run:
-```
-$ curl --request POST https://sym-upload-api/uploads:create?key=myfancysecret123
-```
-
-Which returns `upload_url` "https://upload-server/42?creds=shhhhh" and
-`upload_key` "42". Next you upload the file directly like:
-```
-$ curl -T path/to/file_name "https://upload-server/42?creds=shhhhh"
-```
-
-Once the HTTP PUT is complete, run:
-```
-$ curl --header "Content-Type: application/json" \
-    --request POST \
-    --data '{symbol_id:{"debugFile":"file_name",'\
-        '"debugId":"123123123123123123123123123"}}' \
-    https://sym-upload-api/uploads/42:complete?key=myfancysecret123
-```
-
-### Serving the `sym-upload-v2` Protocol
-
-The protocol is currently defined only in HTTP/REST. There are three necessary
-REST operations to implement in your service:
-* `/symbols/<debug_file>/<debug_id>:checkStatus?key=<key>`
-* `/uploads:create?key=<key>`
-* `/uploads/<upload_key>:complete?key=<key>`
-
-#### Authenticate Using `key`
-
-The query string arg `key` contains some secret that both the uploader and
-server understand. It is up to the service implementer to decide on what
-constitutes a valid `key`, how the uploader acquires one, and how to handle
-requests made with invalid ones.
-
-#### Symbol `checkStatus`
-
-```
-/symbols/<debug_file>/<debug_id>:checkStatus?key=<key>
-```
-
-This operation expects an empty (or no) JSON payload in the request.
-
-This operation should return the status of the symbol file uniquely identified
-by the given `debug_file` and `debug_id`. JSON schema:
-```
-{
-    "type": object",
-    "properties": {
-        "status": {
-            "type": "string",
-            "enum": ["STATUS_UNSPECIFIED", "MISING", "FOUND"],
-            "required": true
-        }
-    }
-}
-```
-
-Where `MISSING` denotes that the symbol file does not exist on the server and
-`FOUND` denotes that the symbol file exists on the server.
-
-#### Upload `create`
-
-```
-/uploads:create?key=<key>
-```
-
-This operation expects an empty (or no) JSON payload in the request.
-
-This operation should return a URL that uploader can HTTP PUT their symbol file
-to, along with an "upload key" that can be used to notify the service once the
-file upload is completed. JSON schema:
-```
-{
-    "type": "object",
-    "properties": {
-        "upload_url": {
-            "type: "string",
-            "required": true
-        },
-        "upload_key": {
-            "type": "string",
-            "required": true
-        }
-    }
-}
-```
-
-Since this REST API operation can be authenticated via the `key` query string
-arg, the service can return a URL that encodes permission delegation to the
-upload endpoint resource and thereby constrain the ability to upload to those
-with valid `key`s.
-
-#### Uploading the Symbol File
-
-Note that the actual symbol upload step is _not_ part of the REST API. The
-upload URL obtained in the above operation is meant to be used as the endpoint
-for a normal HTTP PUT request for the contents of the symbol file. Once that
-HTTP PUT request is completed use the upload `complete` operation.
-
-#### Upload `complete`
-
-```
-/uploads/<upload_key>:complete?key=<key>
-```
-
-This operation expects a JSON payload in the HTTP request body with the
-following schema:
-```
-{
-    "type": "object",
-    "properties": {
-        "symbol_id": {
-            "type": "object",
-            "properties": {
-                "debug_file": {
-                    "type": "string",
-                    "required": true
-                },
-                "debug_id": {
-                    "type": "string",
-                    "required": true
-                }
-            }
-        }
-    }
-}
-```
-
-This operation should cause the symbol storage back-end (however implemented)
-to consume the symbol file identified by `upload_key`. It is up to the service
-implementation to decide how uploads are assigned `upload_key`s and how to
-retrieve a completed upload by its `upload_key`. If the symbol file cannot be
-found, is malformed, or the operation cannot be completed for any other reason
-then an HTTP error will be returned. JSON schema of non-error responses:
-```
-{
-    "type": "object",
-    "properties": {
-        "result": {
-            "type": string,
-            "enum": ["RESULT_UNSPECIFIED", "OK", "DUPLICATE_DATA"],
-            "required": true
-        }
-    }
-}
-```
-
-Where `OK` denotes that the symbol storage was updated with the new symbol file
-and `DUPLICATE_DATA` denotes that the symbol file data was identical to data
-already in symbol storage and therefore nothing changed.
@@ -1,506 +0,0 @@
-# Introduction
-
-Given a minidump file, the Breakpad processor produces stack traces that include
-function names and source locations. However, minidump files contain only the
-byte-by-byte contents of threads' registers and stacks, without function names
-or machine-code-to-source mapping data. The processor consults Breakpad symbol
-files for the information it needs to produce human-readable stack traces from
-the binary-only minidump file.
-
-The platform-specific symbol dumping tools parse the debugging information the
-compiler provides (whether as DWARF or STABS sections in an ELF file or as
-stand-alone PDB files), and write that information back out in the Breakpad
-symbol file format. This format is much simpler and less detailed than compiler
-debugging information, and values legibility over compactness.
-
-# Overview
-
-Breakpad symbol files are ASCII text files, with lines delimited as appropriate
-for the host platform. Each line is a _record_, divided into fields by single
-spaces; in some cases, the last field of the record can contain spaces. The
-first field is a string indicating what sort of record the line represents
-(except for line records; these are very common, making them the default saves
-space). Some fields hold decimal or hexadecimal numbers; hexadecimal numbers
-have no "0x" prefix, and use lower-case letters.
-
-Breakpad symbol files contain the following record types. With some
-restrictions, these may appear in any order.
-
-*   A `MODULE` record describes the executable file or shared library from which
-    this data was derived, for use by symbol suppliers. A `MODULE' record should
-    be the first record in the file.
-
-*   A `FILE` record gives a source file name, and assigns it a number by which
-    other records can refer to it.
-
-*   A `FUNC` record describes a function present in the source code.
-
-*   A line record indicates to which source file and line a given range of
-    machine code should be attributed. The line is attributed to the function
-    defined by the most recent `FUNC` record.
-
-*   A `PUBLIC` record gives the address of a linker symbol.
-
-*   A `STACK` record provides information necessary to produce stack traces.
-
-# `MODULE` records
-
-A `MODULE` record provides meta-information about the module the symbol file
-describes. It has the form:
-
-> `MODULE` _operatingsystem_ _architecture_ _id_ _name_
-
-For example: `MODULE Linux x86 D3096ED481217FD4C16B29CD9BC208BA0 firefox-bin
-` These records provide meta-information about the executable or shared library
-from which this symbol file was generated. A symbol supplier might use this
-information to find the correct symbol files to use to interpret a given
-minidump, or to perform other sorts of validation. If present, a `MODULE` record
-should be the first line in the file.
-
-The fields are separated by spaces, and cannot contain spaces themselves, except
-for _name_.
-
-*   The _operatingsystem_ field names the operating system on which the
-    executable or shared library was intended to run. This field should have one
-    of the following values: | **Value** | **Meaning** |
-    |:----------|:--------------------| | Linux | Linux | | mac | Macintosh OSX
-    | | windows | Microsoft Windows |
-
-*   The _architecture_ field indicates what processor architecture the
-    executable or shared library contains machine code for. This field should
-    have one of the following values: | **Value** | **Instruction Set
-    Architecture** | |:----------|:---------------------------------| | x86 |
-    Intel IA-32 | | x86\_64 | AMD64/Intel 64 | | ppc | 32-bit PowerPC | | ppc64
-    | 64-bit PowerPC | | unknown | unknown |
-
-*   The _id_ field is a sequence of hexadecimal digits that identifies the exact
-    executable or library whose contents the symbol file describes. The way in
-    which it is computed varies from platform to platform.
-
-*   The _name_ field contains the base name (the final component of the
-    directory path) of the executable or library. It may contain spaces, and
-    extends to the end of the line.
-
-# `FILE` records
-
-A `FILE` record holds a source file name for other records to refer to. It has
-the form:
-
-> `FILE` _number_ _name_
-
-For example: `FILE 2 /home/jimb/mc/in/browser/app/nsBrowserApp.cpp
-`
-
-A `FILE` record provides the name of a source file, and assigns it a number
-which other records (line records, in particular) can use to refer to that file
-name. The _number_ field is a decimal number. The _name_ field is the name of
-the file; it may contain spaces.
-
-# `FUNC` records
-
-A `FUNC` record describes a source-language function. It has the form:
-
-> `FUNC` _[m]_ _address_ _size_ _parameter\_size_ _name_
-
-For example: `FUNC m c184 30 0 nsQueryInterfaceWithError::operator()(nsID const&,
-void**) const
-`
-
-The _m_ field is optional. If present it indicates that multiple symbols
-reference this function's instructions. (In which case, only one symbol name is
-mentioned within the breakpad file.) Multiple symbols referencing the same
-instructions may occur due to identical code folding by the linker.
-
-The _address_ and _size_ fields are hexadecimal numbers indicating the start
-address and length in bytes of the machine code instructions the function
-occupies. (Breakpad symbol files cannot accurately describe functions whose code
-is not contiguous.) The start address is relative to the module's load address.
-
-The _parameter\_size_ field is a hexadecimal number indicating the size, in
-bytes, of the arguments pushed on the stack for this function. Some calling
-conventions, like the Microsoft Windows `stdcall` convention, require the called
-function to pop parameters passed to it on the stack from its caller before
-returning. The stack walker uses this value, along with data from `STACK`
-records, to step from the called function's frame to the caller's frame.
-
-The _name_ field is the name of the function. In languages that use linker
-symbol name mangling like C++, this should be the source language name (the
-"unmangled" form). This field may contain spaces.
-
-# Line records
-
-A line record describes the source file and line number to which a given range
-of machine code should be attributed. It has the form:
-
-> _address_ _size_ _line_ _filenum_
-
-For example: `c184 7 59 4
-`
-
-Because they are so common, line records do not begin with a string indicating
-the record type. All other record types' names use upper-case letters;
-hexadecimal numbers, like a line record's _address_, use lower-case letters.
-
-The _address_ and _size_ fields are hexadecimal numbers indicating the start
-address and length in bytes of the machine code. The address is relative to the
-module's load address.
-
-The _line_ field is the line number to which the machine code should be
-attributed, in decimal; the first line of the source file is line number 1. The
-_filenum_ field is a decimal number appearing in a prior `FILE` record; the name
-given in that record is the source file name for the machine code.
-
-The line is assumed to belong to the function described by the last preceding
-`FUNC` record. Line records may not appear before the first `FUNC' record.
-
-No two line records in a symbol file cover the same range of addresses. However,
-there may be many line records with identical line and file numbers, as a given
-source line may contribute many non-contiguous blocks of machine code.
-
-# `PUBLIC` records
-
-A `PUBLIC` record describes a publicly visible linker symbol, such as that used
-to identify an assembly language entry point or region of memory. It has the
-form:
-
-> PUBLIC _[m]_ _address_ _parameter\_size_ _name_
-
-For example: `PUBLIC m 2160 0 Public2_1
-`
-
-The Breakpad processor essentially treats a `PUBLIC` record as defining a
-function with no line number data and an indeterminate size: the code extends to
-the next address mentioned. If a given address is covered by both a `PUBLIC`
-record and a `FUNC` record, the processor uses the `FUNC` data.
-
-The _m_ field is optional. If present it indicates that multiple symbols
-reference this function's instructions. (In which case, only one symbol name is
-mentioned within the breakpad file.) Multiple symbols referencing the same
-instructions may occur due to identical code folding by the linker.
-
-The _address_ field is a hexadecimal number indicating the symbol's address,
-relative to the module's load address.
-
-The _parameter\_size_ field is a hexadecimal number indicating the size of the
-parameters passed to the code whose entry point the symbol marks, if known. This
-field has the same meaning as the _parameter\_size_ field of a `FUNC` record;
-see that description for more details.
-
-The _name_ field is the name of the symbol. In languages that use linker symbol
-name mangling like C++, this should be the source language name (the "unmangled"
-form). This field may contain spaces.
-
-# `STACK WIN` records
-
-Given a stack frame, a `STACK WIN` record indicates how to find the frame that
-called it. It has the form:
-
-> STACK WIN _type_ _rva_ _code\_size_ _prologue\_size_ _epilogue\_size_
-> _parameter\_size_ _saved\_register\_size_ _local\_size_ _max\_stack\_size_
-> _has\_program\_string_ _program\_string\_OR\_allocates\_base\_pointer_
-
-For example: `STACK WIN 4 2170 14 1 0 0 0 0 0 1 $eip 4 + ^ = $esp $ebp 8 + =
-$ebp $ebp ^ =
-`
-
-All fields of a `STACK WIN` record, except for the last, are hexadecimal
-numbers.
-
-The _type_ field indicates what sort of stack frame data this record holds. Its
-value should be one of the values of the
-[StackFrameTypeEnum](http://msdn.microsoft.com/en-us/library/bc5207xw%28VS.100%29.aspx)
-type in Microsoft's
-[Debug Interface Access (DIA)](http://msdn.microsoft.com/en-us/library/x93ctkx8%28VS.100%29.aspx) API.
-Breakpad uses only records of type 4 (`FrameTypeFrameData`) and 0
-(`FrameTypeFPO`); it ignores others. These types differ only in whether the last
-field is an _allocates\_base\_pointer_ flag (`FrameTypeFPO`) or a program string
-(`FrameTypeFrameData`). If more than one record covers a given address, Breakpad
-prefers `FrameTypeFrameData` records over `FrameTypeFPO` records.
-
-The _rva_ and _code\_size_ fields give the starting address and length in bytes
-of the machine code covered by this record. The starting address is relative to
-the module's load address.
-
-The _prologue\_size_ and _epilogue\_size_ fields give the length, in bytes, of
-the prologue and epilogue machine code within the record's range. Breakpad does
-not use these values.
-
-The _parameter\_size_ field gives the number of argument bytes this function
-expects to have been passed. This field has the same meaning as the
-_parameter\_size_ field of a `FUNC` record; see that description for more
-details.
-
-The _saved\_register\_size_ field gives the number of bytes in the stack frame
-dedicated to preserving the values of any callee-saves registers used by this
-function.
-
-The _local\_size_ field gives the number of bytes in the stack frame dedicated
-to holding the function's local variables and temporary values.
-
-The _max\_stack\_size_ field gives the maximum number of bytes pushed on the
-stack in the frame. Breakpad does not use this value.
-
-If the _has\_program\_string_ field is zero, then the `STACK WIN` record's final
-field is an _allocates\_base\_pointer_ flag, as a hexadecimal number; this is
-expected for records whose _type_ is 0. Otherwise, the final field is a program
-string.
-
-## Interpreting a `STACK WIN` record
-
-Given the register values for a frame F, we can find the calling frame as
-follows:
-
-*   If the _has\_program\_string_ field of a `STACK WIN` record is zero, then
-    the final field is _allocates\_base\_pointer_, a flag indicating whether the
-    frame uses the frame pointer register, `%ebp`, as a general-purpose
-    register.
-    *   If _allocates\_base\_pointer_ is true, then `%ebp` does not point to the
-        frame's base address. Instead,
-        *   Let _next\_parameter\_size_ be the parameter size of the function
-            frame F called (**not** this record's _parameter\_size_ field), or
-            zero if F is the youngest frame on the stack. You must find this
-            value in F's callee's `FUNC`, `STACK WIN`, or `PUBLIC` records.
-        *   Let _frame\_size_ be the sum of the _local\_size_ field, the
-            _saved\_register\_size_ field, and _next\_parameter\_size_. > > With
-            those definitions in place, we can recover the calling frame as
-            follows:
-        *   F's return address is at `%esp +`_frame\_size_,
-        *   the caller's value of `%ebp` is saved at `%esp
-            +`_next\_parameter\_size_`+`_saved\_register\_size_`- 8`, and
-        *   the caller's value of `%esp` just before the call instruction was
-            `%esp +`_frame\_size_`+ 4`. > > (Why do we include
-            _next\_parameter\_size_ in the sum when computing _frame\_size_ and
-            the address of the saved `%ebp`? When a function A has called a
-            function B, the arguments that A pushed for B are considered part of
-            A's stack frame: A's value for `%esp` points at the last argument
-            pushed for B. Thus, we must include the size of those arguments
-            (given by the debugging info for B) along with the size of A's
-            register save area and local variable area (given by the debugging
-            info for A) when computing the overall size of A's frame.)
-    *   If _allocates\_base\_pointer_ is false, then F's function doesn't use
-        `%ebp` at all. You may recover the calling frame as above, except that
-        the caller's value of `%ebp` is the same as F's value for `%ebp`, so no
-        steps are necessary to recover it.
-*   If the _has\_program\_string_ field of a `STACK WIN` record is not zero,
-    then the record's final field is a string containing a program to be
-    interpreted to recover the caller's frame. The comments in the
-    [postfix\_evaluator.h](../src/processor/postfix_evaluator.h#40)
-    header file explain the language in which the program is written. You should
-    place the following variables in the dictionary before interpreting the
-    program:
-    *   `$ebp` and `$esp` should be the values of the `%ebp` and `%esp`
-        registers in F.
-    *   `.cbParams`, `.cbSavedRegs`, and `.cbLocals`, should be the values of
-        the `STACK WIN` record's _parameter\_size_, _saved\_register\_size_, and
-        _local\_size_ fields.
-    *   `.raSearchStart` should be set to the address on the stack to begin
-        scanning for a return address, if necessary. The Breakpad processor sets
-        this to the value of `%esp` in F, plus the _frame\_size_ value mentioned
-        above.
-
-> If the program stores values for `$eip`, `$esp`, `$ebp`, `$ebx`, `$esi`, or
-> `$edi`, then those are the values of the given registers in the caller. If the
-> value of `$eip` is zero, that indicates that the end of the stack has been
-> reached.
-
-The Breakpad processor checks that the value yielded by the above for the
-calling frame's instruction address refers to known code; if the address seems
-to be bogus, then it uses a heuristic search to find F's return address and
-stack base.
-
-# `STACK CFI` records
-
-`STACK CFI` ("Call Frame Information") records describe how to walk the stack
-when execution is at a given machine instruction. These records take one of two
-forms:
-
-> `STACK CFI INIT` _address_ _size_ _register<sub>1</sub>_:
-> _expression<sub>1</sub>_ _register<sub>2</sub>_: _expression<sub>2</sub>_ ...
->
-> `STACK CFI` _address_ _register<sub>1</sub>_: _expression<sub>1</sub>_
-> _register<sub>2</sub>_: _expression<sub>2</sub>_ ...
-
-For example:
-
-```
-STACK CFI INIT 804c4b0 40 .cfa: $esp 4 + $eip: .cfa 4 - ^
-STACK CFI 804c4b1 .cfa: $esp 8 + $ebp: .cfa 8 - ^
-```
-
-The _address_ and _size_ fields are hexadecimal numbers. Each
-_register_<sub>i</sub> is the name of a register or pseudoregister. Each
-_expression_ is a Breakpad postfix expression, which may contain spaces, but
-never ends with a colon. (The appropriate register names for a given
-architecture are determined when `STACK CFI` records are first enabled for that
-architecture, and should be documented in the appropriate
-`stackwalker_`_architecture_`.cc` source file.)
-
-STACK CFI records describe, at each machine instruction in a given function, how
-to recover the values the machine registers had in the function's caller.
-Naturally, some registers' values are simply lost, but there are three cases in
-which they can be recovered:
-
-*   You can always recover the program counter, because that's the function's
-    return address. If the function is ever going to return, the PC must be
-    saved somewhere.
-
-*   You can always recover the stack pointer. The function is responsible for
-    popping its stack frame before it returns to the caller, so it must be able
-    to restore this, as well.
-
-*   You should be able to recover the values of callee-saves registers. These
-    are registers whose values the callee must preserve, either by saving them
-    in its own stack frame before using them and re-loading them before
-    returning, or by not using them at all.
-
-(As an exception, note that functions which never return may not save any of
-this data. It may not be possible to walk the stack past such functions' stack
-frames.)
-
-Given rules for recovering the values of a function's caller's registers, we can
-walk up the stack. Starting with the current set of registers --- the PC of the
-instruction we're currently executing, the current stack pointer, etc. --- we
-use CFI to recover the values those registers had in the caller of the current
-frame. This gives us a PC in the caller whose CFI we can look up; we apply the
-process again to find that function's caller; and so on.
-
-Concretely, CFI records represent a table with a row for each machine
-instruction address and a column for each register. The table entry for a given
-address and register contains a rule describing how, when the PC is at that
-address, to restore the value that register had in the caller.
-
-There are some special columns:
-
-*   A column named `.cfa`, for "Canonical Frame Address", tells how to compute
-    the base address of the frame; other entries can refer to the CFA in their
-    rules.
-
-*   A column named `.ra` represents the return address.
-
-For example, suppose we have a machine with 32-bit registers, one-byte
-instructions, a stack that grows downwards, and an assembly language that
-resembles C. Suppose further that we have a function whose machine code looks
-like this:
-
-```
-func:                                ; entry point; return address at sp
-func+0:      sp -= 16                ; allocate space for stack frame
-func+1:      sp[12] = r0             ; save 4-byte r0 at sp+12
-             ...                     ; stuff that doesn't affect stack
-func+10:     sp -= 4; *sp = x        ; push some 4-byte x on the stack
-             ...                     ; stuff that doesn't affect stack
-func+20:     r0 = sp[16]             ; restore saved r0
-func+21:     sp += 20                ; pop whole stack frame
-func+22:     pc = *sp; sp += 4       ; pop return address and jump to it
-```
-
-The following table would describe the function above:
-
-**code address** | **.cfa** | **r0 (on Google Code)** | **r1 (on Google Code)** | ... | **.ra**
-:--------------- | :------- | :---------------------- | :---------------------- | :-- | :-------
-func+0           | sp       |                         |                         |     | `cfa[0]`
-func+1           | sp+16    |                         |                         |     | `cfa[0]`
-func+2           | sp+16    | `cfa[-4]`               |                         |     | `cfa[0]`
-func+11          | sp+20    | `cfa[-4]`               |                         |     | `cfa[0]`
-func+21          | sp+20    |                         |                         |     | `cfa[0]`
-func+22          | sp       |                         |                         |     | `cfa[0]`
-
-Some things to note here:
-
-*   Each row describes the state of affairs **before** executing the instruction
-    at the given address. Thus, the row for func+0 describes the state before we
-    execute the first instruction, which allocates the stack frame. In the next
-    row, the formula for computing the CFA has changed, reflecting the
-    allocation.
-
-*   The other entries are written in terms of the CFA; this allows them to
-    remain unchanged as the stack pointer gets bumped around. For example, to
-    find the caller's value for r0 (on Google Code) at func+2, we would first
-    compute the CFA by adding 16 to the sp, and then subtract four from that to
-    find the address at which r0 (on Google Code) was saved.
-
-*   Although the example doesn't show this, most calling conventions designate
-    "callee-saves" and "caller-saves" registers. The callee must restore the
-    values of "callee-saves" registers before returning (if it uses them at
-    all), whereas the callee is free to use "caller-saves" registers without
-    restoring their values. A function that uses caller-saves registers
-    typically does not save their original values at all; in this case, the CFI
-    marks such registers' values as "unrecoverable".
-
-*   Exactly where the CFA points in the frame --- at the return address? below
-    it? At some fixed point within the frame? --- is a question of definition
-    that depends on the architecture and ABI in use. But by definition, the CFA
-    remains constant throughout the lifetime of the frame. It's up to
-    architecture- specific code to know what significance to assign the CFA, if
-    any.
-
-To save space, the most common type of CFI record only mentions the table
-entries at which changes take place. So for the above, the CFI data would only
-actually mention the non-blank entries here:
-
-**insn** | **cfa** | **r0 (on Google Code)** | **r1 (on Google Code)** | ... | **ra**
-:------- | :------ | :---------------------- | :---------------------- | :-- | :-------
-func+0   | sp      |                         |                         |     | `cfa[0]`
-func+1   | sp+16   |                         |                         |     |
-func+2   |         | `cfa[-4]`               |                         |     |
-func+11  | sp+20   |                         |                         |     |
-func+21  |         | r0 (on Google Code)     |                         |     |
-func+22  | sp      |                         |                         |     |
-
-A `STACK CFI INIT` record indicates that, at the machine instruction at
-_address_, belonging to some function, the value that _register<sub>n</sub>_ had
-in that function's caller can be recovered by evaluating
-_expression<sub>n</sub>_. The values of any callee-saves registers not mentioned
-are assumed to be unchanged. (`STACK CFI` records never mention caller-saves
-registers.) These rules apply starting at _address_ and continue up to, but not
-including, the address given in the next `STACK CFI` record. The _size_ field is
-the total number of bytes of machine code covered by this record and any
-subsequent `STACK CFI` records (until the next `STACK CFI INIT` record). The
-_address_ field is relative to the module's load address.
-
-A `STACK CFI` record (no `INIT`) is the same, except that it mentions only those
-registers whose recovery rules have changed from the previous CFI record. There
-must be a prior `STACK CFI INIT` or `STACK CFI` record in the symbol file. The
-_address_ field of this record must be greater than that of the previous record,
-and it must not be at or beyond the end of the range given by the most recent
-`STACK CFI INIT` record. The address is relative to the module's load address.
-
-Each expression is a breakpad-style postfix expression. Expressions may contain
-spaces, but their tokens may not end with colons. When an expression mentions a
-register, it refers to the value of that register in the callee, even if a prior
-name/expression pair gives that register's value in the caller. The exception is
-`.cfa`, which refers to the canonical frame address computed by the .cfa rule in
-force at the current instruction.
-
-The special expression `.undef` indicates that the given register's value cannot
-be recovered.
-
-The register names preceding the expressions are always followed by colons. The
-expressions themselves never contain tokens ending with colons.
-
-There are two special register names:
-
-*   `.cfa` ("Canonical Frame Address") is the base address of the stack frame.
-    Other registers' rules may refer to this. If no rule is provided for the
-    stack pointer, the value of `.cfa` is the caller's stack pointer.
-
-*   `.ra` is the return address. This is the value of the restored program
-    counter. We use `.ra` instead of the architecture-specific name for the
-    program counter.
-
-The Breakpad stack walker requires that there be rules in force for `.cfa` and
-`.ra` at every code address from which it unwinds. If those rules are not
-present, the stack walker will ignore the `STACK CFI` data, and try to use a
-different strategy.
-
-So the CFI for the example function above would be as follows, if `func` were at
-address 0x1000 (relative to the module's load address):
-
-```
-STACK CFI INIT 1000 .cfa: $sp .ra: .cfa ^
-STACK CFI      1001 .cfa: $sp 16 +
-STACK CFI      1002 $r0: .cfa 4 - ^
-STACK CFI      100b .cfa: $sp 20 +
-STACK CFI      1015 $r0: $r0
-STACK CFI      1016 .cfa: $sp
-```