tdbc::sqlite3

Ticket Change Details
Login
Bounty program for improvements to Tcl and certain Tcl packages.
Tcl 2018 Conference, Houston/TX, US, Oct 15-19
Send your abstracts to tclconference@googlegroups.com
or submit via the online form by Aug 20.
Overview

Artifact ID: 321fcaef6971558fb605770eac0228daa0601beceaa9cb2bb071b9a2ef86fec3
Ticket: b0dc2249a23380b9faa94ab9430ed41f5101f7d5
Segfault on MacOS 10.12.6
User & Date: anonymous 2018-08-19 15:06:20
Changes

  1. Change icomment to:

    It turns out my analysis was a bit premature. Yes, when trying to "make test" it segfaults, and yes, this seems to depend on the sqlite3 package, but no, it is not the sqlite3 3.9.2 package that was built that segfaults; what segfaults is a sqlite3 3.16.0 package Apple bundled with the OS. If forcing a load of 3.9.2 it works fine (AFAICT; I haven't figured out how to make the tests do that, just ran tdbc::sqlite3::connection create and some other commands manually in a Tcl shell, not seeing anything wrong).

    There still is a bug, namely that "make test" isn't testing the package we built but some random higher version-numbered package it happens to find already installed, however that probably isn't a critical error.

    There is also a gotcha, that this OS-provided package (the ifneeded script reads load /System/Library/Tcl/sqlite3/libtclsqlite3.dylib Tclsqlite3) is out there and disrupts things, but that's not something the TDBC maintainers can do anything about directly. (Although updating the bundled sqlite3 version should help.)

  2. Change login to "anonymous"
  3. Change mimetype to "text/x-fossil-plain"
  4. Change priority to "Immediate"
  5. Change resolution to "Open"
  6. Change severity to "Severe"
  7. Change subsystem to "not_specified"
  8. Change type to "Build_Problem"
  9. Change username to "Lars H"