Jean-Claude Wippler | 16 Jun 10:53

New svn repository, release 2.4.9.7


The Metakit CVS repository has been migrated to Subversion.
The latest source code can now be obtained as follows:

	svn co svn://svn.equi4.com/metakit/trunk metakit

Snapshots of previous releases are in .../metakit/tags/...

A tar file is available from:
	http://www.equi4.com/pub/mk/metakit-2.4.9.7.tar.gz

In addition, an new release was made to fix bugs in Mk4tcl.
This update only affects Metakit with Tcl in threaded mode.
Below is the corresponding section of the change log.

-jcw

2007-06-16    ############################################    MK 2.4.9.7

     If you're using Tcl in threaded mode, please upgrade - see below.

2007-06-16    Fix threading problems in Mk4tcl

     The Mk4tcl binding had two serious bugs, causing potential crashes
     and database corruption when used in multi-threaded mode:

     1) The Makefile did not set -DTCL_THREADS when configured with
        the "--enable-threads" flag, only -Dq4_MULTI, which is the C++
        level threading support of Metakit.  So all builds were still
        running the Mk4tcl wrapper in unprotected mode (!).

     2) Tcl's type conversion callbacks did not contain mutex calls to
        prevent calls from Tcl into Mk4tcl other than mk::* commands.
        This happens during "Tcl_ObjType mkCursorType" type conversions.

     Added the proper -DTCL_THREADS flag to Makefile.in, and extra code
     to implement recursive mutex protection on top of Tcl's primitives.

     This problem does not affect the C++ core (which has been in use in
     threaded mode for some time, on many platforms including Windows),
     nor the Mk4py binding for Python which uses a global interp lock.

2007-02-12    Continue unmapped, also in debug mode

     In the WIN32 version of ResetFileMapping, there were two assertions
     which made the code fail in debug builds, even though both cases  
are
     properly handled with if's.  Dropped the asserts, so that the logic
     is the same as in release builds: when memory mapping fails, simply
     continue without memory mapping and fall back to buffering all  
data.

2006-11-15    ############################################    MK 2.4.9.6

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "metakit" group.
To post to this group, send email to metakit <at> googlegroups.com
To unsubscribe from this group, send email to metakit-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/metakit?hl=en
-~----------~----~----~----~------~----~------~--~---


Gmane