Tcl Source Code

Ticket Change Details
Bounty program for improvements to Tcl and certain Tcl packages.
Tcl 2019 Conference, Houston/TX, US, Nov 4-8
Send your abstracts to [email protected]
or submit via the online form by Sep 9.

Artifact ID: 5c8a55da0d07ec9d98249ea5fdef84910cc1a969
Ticket: 293344d4f3e07f7f9da93db4b967abed8122bd42
Regression in SQLite test-suite
User & Date: jan.nijtmans 2017-07-13 15:00:42

  1. Change assignee to "nobody"
  2. Change closer to "nobody"
  3. Change cmimetype to "text/x-fossil-wiki"
  4. Change comment to:

    When running the latest SQLite test-suite there was a regression in 2 test-cases, one of them: badutf2-4.1.5... ! badutf2-4.1.5 expected: [\u0080] ! badutf2-4.1.5 got: [\uFF80]

    bisecting Tcl pointed to commit [7351fc0c9c], but - actually - there's nothing wrong with this commit. Further investigation resulted in the observation that the macro TclUtfToUniChar() contained a mistake: If 'str' points to a signed character (which it normally does), a character in the range \x80-\xC0 results in an unicode character in the range \xFF80-\xFFC0 ... this is clearly wrong.

    Conclusion: this is a long-standing bug in the TclUtfToUniChar() macro, which was never discovered because there was no test-case touching this. Commit [7351fc0c9c] merely exposed this bug in the SQLite test-suite.

  5. Change foundin to "core-8-6-branch"
  6. Change is_private to "0"
  7. Change login to "jan.nijtmans"
  8. Change priority to "5 Medium"
  9. Change resolution to "None"
  10. Change severity to "Minor"
  11. Change status to "Open"
  12. Change submitter to "jan.nijtmans"
  13. Change subsystem to "- New Builtin Commands"
  14. Change title to "Regression in SQLite test-suite"
  15. Change type to "Bug"