Jason Toffaletti
Jason Toffaletti
If you have many Benchmark: ``` let benchmarks : @Sendable () -> Void = { ```
I am seeing similar issues where duckdb-swift crashes in very odd ways only in release mode: ``` * thread #2, queue = 'com.apple.root.default-qos.cooperative', stop reason = EXC_BAD_ACCESS (code=1, address=0x180) frame...
That last crash stuck in my head. I'm wondering if `-pthread` is missing when building `Cduckdb`? I'm not seeing it explicitly in the output with `-v`, but maybe it is...
This is super weird, notice: `ptr = 0x180 {}` ``` (lldb) p stmt (DuckDB.PreparedStatement) 0x0000000154008390 { connection = 0x0000600003276b80 { database = 0x0000600003269700 { ptr = 0x600003068190 { pointee =...
Neither thread sanitizer or address sanitizer find any errors before the crash... ``` AddressSanitizer:DEADLYSIGNAL ================================================================= ==50191==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000180 (pc 0x0001062ff534 bp 0x00016d85acc0 sp 0x00016d85aca0 T-1) ==50191==The...
I'm pretty sure it is a compiler bug. I switched to a swift 6 nightly and the crash went away in most places in the code, except for one. Stepping...
In a debug build this all works as expected: ``` 74 Connection *conn = reinterpret_cast(connection); 75 wrapper->statement = conn->Prepare(query); 76 *out_prepared_statement = (duckdb_prepared_statement)wrapper; -> 77 return !wrapper->statement->HasError() ? DuckDBSuccess :...
I have the Swift 6 snapshot from 6/12 so I'm a bit out of date. I'll try updating to see if I run into the same issue and I can...
It was a compiler bug. https://github.com/swiftlang/swift/pull/74969 The workaround for now is to add -Xllvm -sil-disable-pass=stack-promotion
I was able to get it to work using pixi with this `pyproject.toml`, put it in the repo root: ``` [project] dependencies = [ "gguf>=0.1.0", "numpy~=1.26.4", "protobuf>=4.21.0,=4.46.3,= 3.9" version =...