-
sdeasey changed the public information on the NaviServer project.
2009-02-04 22:02:40 UTC in NaviServer
-
sdeasey changed the public information on the NaviServer project.
2009-02-04 21:59:12 UTC in NaviServer
-
sdeasey changed the public information on the NaviServer project.
2009-02-04 21:57:24 UTC in NaviServer
-
With Tcl from HEAD compiled:
--enable-threads --enable-symbols=mem
on a modern 32bit Linux, a program (naviserver) linked with that Tcl aborts with this message:
Tcl_GetMemoryInfo called when threaded memory allocator not in use
Yet the tclConfig.sh contains:
-DTCL_THREADS=1
-DUSE_THREAD_ALLOC=1
And the symbol USE_THREAD_ALLOC, which this feature depends on, seems to...
2008-11-25 19:58:24 UTC in Tcl
-
> can you confirm this is fixed in Tcl 8.6a3 ?
Hmm, probably... :-)
I updated to HEAD and my test program works.
However, there seems to be a new build oddity. Naviserver, compiled with either no flags to it's autogen.sh script, or with --enable-symbols results in the same error. Compiling with --enable-symbols=mem, the same as Tcl, now gets passed this error.
Has the Tcl build system...
2008-11-24 23:32:06 UTC in Tcl
-
Yes, threaded (isn't that the default these days), like this:
--enable-threads --enable-symbols=mem
This is on a modern 32bit Linux.
2008-11-24 22:04:13 UTC in Tcl
-
The change in behaviour first appeared on 2003-07-21 when Mo DeJong checked in some changes to catch Tcl objects moving between interps with mem debugging enabled.
Here is a minimal failing program:
int
main(int argc, char **argv)
{
Tcl_Interp *interp;
Tcl_Obj *objPtr;
Tcl_FindExecutable(argv[0]);
objPtr = Tcl_NewObj();
Tcl_DecrRefCount(objPtr);
interp =...
2008-11-24 21:35:51 UTC in Tcl
-
I used to test against 8.5 before it was released but it was taking a while so it dropped off my radar. It definitely worked at one point, as I always test with --enable-symbols=mem.
I just grabbed the 8.5.0 tarball -- same problem.
Looking around I see I have 8.5a5 still installed, whos tcl.h has this tag:
RCS: @(#) $Id: tcl.h,v 1.214 2006/08/18 07:45:31 das Exp $
Same problem :-(
Hmm...
2008-11-22 19:16:49 UTC in Tcl
-
Naviserver fails in early startup with the message:
"expected to create a new entry for object map"
when compiled against tcl8.5.5 and --enable-symbols=mem. It works fine with just --enable-symbols.
It works fine either way with tcl8.4.19.
Here's a backtrace:
Fatal: expected to create new entry for object map
#0 0x00110416 in __kernel_vsyscall ()
#1 0x00b42660 in raise (...
2008-11-22 06:20:46 UTC in Tcl
-
I don't think this bug is fixed.
Ticket was closed 2008-05-30, and tcl-8.5.5 was released 2008-10-15.
I'm experiencing this (or a very similar bug) with tcl8.5.5.
It occurs very early in the startup of naviserver.
Here's a backtrace:
Fatal: expected to create new entry for object map
#0 0x00110416 in __kernel_vsyscall ()
#1 0x00b42660 in raise () from /lib/libc.so.6
#2...
2008-11-21 21:00:34 UTC in Tcl