Verify in the GitHub workflow that cv2pdb can handle GCC's output

Git for Windows uses cv2pdb to convert the debugging information
produced by GCC to `.pdb` format, for use with Visual C's tools.

A recent GCC upgrade broke this because the debugging information was
produced in DWARF5 format, and the Git for Windows maintainer had to
scramble to implement (minimal) support for that format.

Let's verify in the GitHub workflow that cv2pdb can handle GCC's output
format, and let's use the very same GCC version that Git for Windows
uses to verify that.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

1 files changed, 28 insertions, 1 deletions

diff --git a/.github/workflows/build-and-test.yml b/.github/workflows/build-and-test.yml
index 035237e..9cfcbcc 100644
--- a/.github/workflows/build-and-test.yml
+++ b/.github/workflows/build-and-test.yml
@@ -1,4 +1,4 @@
-name: build cv2pdb
+name: build and test cv2pdb
 
 on: [push, pull_request]
 
@@ -26,3 +26,30 @@ jobs:
         with:
           name: bin
           path: bin
+  test-with-g4w-sdk:
+    runs-on: windows-latest
+    needs: build
+    steps:
+      - name: Download bin/
+        uses: actions/download-artifact@v2
+        with:
+          name: bin
+          path: bin
+      - uses: git-for-windows/setup-git-for-windows-sdk@v1
+      - name: verify using Git for Windows' GCC
+        shell: bash
+        run: |
+          set -x &&
+          cat >hello.c <<-\EOF &&
+          #include <stdio.h>
+
+          int main(int argc, char **argv)
+          {
+            printf("Hello, world\n");
+            return 0;
+          }
+          EOF
+
+          gcc -g -o hello.exe hello.c &&
+          bin/${{env.BUILD_CONFIGURATION}}*/cv2pdb.exe hello.exe world.exe &&
+          ls -l hello* world*