rusty_v8

Summary Adds a thin Rust binding for . The new wrapper forwards through a C shim in , matching the existing global API binding style. Validation currently stops on an unrelated existing bindgen constant mismatch in ( vs ).

Summary v8-goose's prebuilt V8 binaries statically link libc++abi which exports C++ exception handling symbols (, , , , etc.). These override the system's libstdc++ symbols at link time on Linux. Result: any other C++ library in the same process that uses libstdc++'s exception handling (via cxxbridge or similar FFI) hits V8's instead of its own catch handler. The exception cannot propagate across the ABI boundary; fires; process aborts. Reproduction Permagent links both v8-goose (via feature) and kuzu (via spectral-graph for graph storage). On Linux (ubuntu-24.04, glibc 2.39), the test binary aborts during kuzu's which uses cxxbridge. In-process backtrace via test-harness SIGABRT handler: Both libc++abi frames are from V8's tree. The exception originates from kuzu (which uses system libstdc++) but is caught by V8's libc++abi terminate handler. macOS is unaffected because it natively uses libc++ (no ABI mismatch). What we ruled out The feature flag — disabling it does NOT fix the issue, because libc++abi is bundled in the prebuilt V8 binary regardless It is not a kuzu-specific bug — kuzu's own test suite runs 138 instances on the same ubuntu-latest runner without abort. The issue only manifests when V8 is linked in the same process It is not a glibc version issue — the abort is link-time symbol resolution, not runtime glibc behavior Bisect data Proposed fix Make V8's libc++abi exception handling symbols hidden ( on the libc++abi build, or a linker version script restricting exported symbols). This would prevent them from overriding the system's at link time, while preserving V8's internal exception handling. This pattern is used by other large C++ runtimes embedded in Rust crates that need to coexist with other C++ FFI libraries. Workaround for downstream consumers Move conflicting tests/code to a separate binary that doesn't link V8. This is what Permagent has done: https://github.com/make-tuned-unit/permagent-runtime/pull/205 Environment OS: Ubuntu 24.04 (glibc 2.39) Rust: stable (1.91.1) v8-goose: 145.0.2 Other C++ deps in process: kuzu 0.11.3 (via cxxbridge)

I discovered an (accidentally) unsound use of unsafe in . The extern declaration doesn't match the actual signature of the v8 function. I've opened a PR to fix it (#1994), but I'm not sure if an unsolicited PR will get noticed (and you have no CONTRIBUTING.md file to suggest the proper way to engage about stuff like this). I am currently using this method in my project, and I would like to get this UB fixed asap.