Date: Sat, 10 Feb 2024 18:57:33 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 276952] databases/duckdb: DuckDB 0.9.2 segfaults with node module Message-ID: <bug-276952-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276952 Bug ID: 276952 Summary: databases/duckdb: DuckDB 0.9.2 segfaults with node module Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: yuri@freebsd.org Reporter: mark@voortman.name Assignee: yuri@freebsd.org Flags: maintainer-feedback?(yuri@freebsd.org) Created attachment 248320 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D248320&action= =3Dedit DuckDB stack trace Steps to reproduce: - Run 'sudo pkg install duckdb node npm' - Run 'npm install --save duckdb' - Create this trivial program as duckdb.js: const duckdb =3D require("duckdb"); const db =3D new duckdb.Database(":memory:", { "access_mode": "READ_WRITE", "threads": "1" }, (err) =3D> { console.log(err); }); - Run 'node duckdb.js' which will fail with a segmentation fault. - The stack trace is attached. - I tried setting threads to "1" to no avail. - I tried on both FreeBSD 13.2 and 14.0 to no avail. - I tried disabling ICU (given the stack trace) in the DuckDB build to no avail. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276952-7788>