add CI workflow for Ruby ASAN (AddressSanitizer) testing

Use `ruby/setup-ruby` with `ruby-version: asan` on
ubuntu-24.04. The LD_PRELOAD libstdc++.so to resolve
`__cxa_throw` ASAN CHECK failure when DuckDB throws
C++ exceptions internally.

See: google/sanitizers#934

Author: otegami

.github/workflows/ruby_asan_on_ubuntu.yml

@@ -0,0 +1,80 @@
+name: Ruby ASAN
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types:
+      - opened
+      - synchronize
+      - reopened
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    runs-on: ubuntu-24.04
+    timeout-minutes: 120
+    strategy:
+      matrix:
+        duckdb: ['1.4.4', '1.3.2']
+
+    steps:
+    - uses: actions/checkout@v6
+
+    - name: Set up Ruby with ASAN
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: asan
+        bundler-cache: true
+
+    - name: duckdb cache
+      id: duckdb-cache
+      uses: actions/cache@v5
+      with:
+        path: duckdb-v${{ matrix.duckdb }}
+        key: ${{ runner.os }}-duckdb-v${{ matrix.duckdb }}
+
+    - name: Build duckdb ${{ matrix.duckdb }}
+      env:
+        DUCKDB_VERSION: ${{ matrix.duckdb }}
+      if: steps.duckdb-cache.outputs.cache-hit != 'true'
+      run: |
+        git clone -b v$DUCKDB_VERSION https://github.com/duckdb/duckdb.git duckdb-tmp-v$DUCKDB_VERSION
+        cd duckdb-tmp-v$DUCKDB_VERSION && make && cd ..
+        rm -rf duckdb-v$DUCKDB_VERSION
+        mkdir -p duckdb-v$DUCKDB_VERSION/build/release/src duckdb-v$DUCKDB_VERSION/src
+        cp -rip duckdb-tmp-v$DUCKDB_VERSION/build/release/src/*.so duckdb-v$DUCKDB_VERSION/build/release/src
+        cp -rip duckdb-tmp-v$DUCKDB_VERSION/src/include duckdb-v$DUCKDB_VERSION/src/
+
+    - name: bundle install
+      env:
+        DUCKDB_VERSION: ${{ matrix.duckdb }}
+      run: |
+        bundle install --jobs 4 --retry 3
+
+    - name: Build with ASAN Ruby
+      env:
+        DUCKDB_VERSION: ${{ matrix.duckdb }}
+      run: |
+        bundle exec rake build -- --with-duckdb-include=${GITHUB_WORKSPACE}/duckdb-v${DUCKDB_VERSION}/src/include --with-duckdb-lib=${GITHUB_WORKSPACE}/duckdb-v${DUCKDB_VERSION}/build/release/src/
+
+    - name: Run tests with ASAN
+      env:
+        DUCKDB_VERSION: ${{ matrix.duckdb }}
+      run: |
+        # LD_PRELOAD resolves __cxa_throw ASAN CHECK failure when DuckDB (built
+        # without ASAN) throws C++ exceptions internally.
+        # See: https://github.com/google/sanitizers/issues/934
+        export LD_PRELOAD="$(realpath "$(gcc -print-file-name=libstdc++.so)")"
+        rake test
+
+  post-test:
+    name: All ASAN tests passed
+    runs-on: ubuntu-latest
+    needs: test
+    steps:
+      - run: echo ok

CHANGELOG.md

@@ -3,6 +3,7 @@
 All notable changes to this project will be documented in this file.
 
 # Unreleased
+- add CI workflow for Ruby ASAN (AddressSanitizer) testing.
 - DuckDB::BindInfo#add_result_column accepts symbols as column, column type argument.
 - add `DuckDB::LogicalType.resolve`.
 - add `DuckDB.cast`.

test/duckdb_test/asan_test.rb

@@ -0,0 +1,40 @@
+# frozen_string_literal: true
+
+require 'test_helper'
+
+# Tests that exercise error paths to verify memory safety under ASAN.
+# These tests ensure that DuckDB's internal C++ exceptions (caught by the C API)
+# do not cause __cxa_throw ASAN CHECK failures with the LD_PRELOAD workaround.
+module DuckDBTest
+  class AsanTest < Minitest::Test
+    def test_open_database_with_invalid_path
+      assert_raises(DuckDB::Error) do
+        DuckDB::Database.open('not_exist_dir/not_exist_file')
+      end
+    end
+
+    def test_prepare_invalid_sql
+      db = DuckDB::Database.open
+      con = db.connect
+      assert_raises(DuckDB::Error) do
+        DuckDB::PreparedStatement.new(con, 'INVALID SQL')
+      end
+    end
+
+    def test_query_nonexistent_table
+      db = DuckDB::Database.open
+      con = db.connect
+      assert_raises(DuckDB::Error) do
+        con.query('SELECT * FROM nonexistent_table')
+      end
+    end
+
+    def test_extract_invalid_statements
+      db = DuckDB::Database.open
+      con = db.connect
+      assert_raises(DuckDB::Error) do
+        DuckDB::ExtractedStatements.new(con, 'INVALID SQL;')
+      end
+    end
+  end
+end