On 11/21/08, Bernd Eidenschink <[EMAIL PROTECTED]> wrote: > > > No no. Errors are bad, there should be none. > > > > Stop teasing and show us them... :-) > > > Here you go: > http://www.kinetiqa.de/naviserver/memcheck.log.txt > > TCL: 8.4.19 sources
This is weird, 8.4 also has errors? (you were using 8.5.5 before?) 8.4.19 works for me. Are you compiling 32bit on a 64bit linux box? Anyway, these kinds of things are usually errors (the message is from valgrind): ==18662== Invalid read of size 4 ==18662== at 0x40151E3: (within /lib/ld-2.7.so) ==18662== by 0x4005C59: (within /lib/ld-2.7.so) ==18662== by 0x4007A87: (within /lib/ld-2.7.so) ==18662== by 0x4011533: (within /lib/ld-2.7.so) ==18662== by 0x400D5C5: (within /lib/ld-2.7.so) ==18662== by 0x4010F4D: (within /lib/ld-2.7.so) ==18662== by 0x41E9C18: (within /lib/tls/i686/cmov/libdl-2.7.so) ==18662== by 0x400D5C5: (within /lib/ld-2.7.so) ==18662== by 0x41EA2BB: (within /lib/tls/i686/cmov/libdl-2.7.so) ==18662== by 0x41E9B50: dlopen (in /lib/tls/i686/cmov/libdl-2.7.so) ==18662== by 0x41CF245: TclpDlopen (tclLoadDl.c:78) ==18662== by 0x419195C: Tcl_FSLoadFile (tclIOUtil.c:2791) ==18662== Address 0x4fd2fc0 is 32 bytes inside a block of size 35 alloc'd ==18662== at 0x4022AB8: malloc (vg_replace_malloc.c:207) ==18662== by 0x4006FC4: (within /lib/ld-2.7.so) ==18662== by 0x40079C9: (within /lib/ld-2.7.so) ==18662== by 0x4011533: (within /lib/ld-2.7.so) ==18662== by 0x400D5C5: (within /lib/ld-2.7.so) ==18662== by 0x4010F4D: (within /lib/ld-2.7.so) ==18662== by 0x41E9C18: (within /lib/tls/i686/cmov/libdl-2.7.so) ==18662== by 0x400D5C5: (within /lib/ld-2.7.so) ==18662== by 0x41EA2BB: (within /lib/tls/i686/cmov/libdl-2.7.so) ==18662== by 0x41E9B50: dlopen (in /lib/tls/i686/cmov/libdl-2.7.so) ==18662== by 0x41CF245: TclpDlopen (tclLoadDl.c:78) ==18662== by 0x419195C: Tcl_FSLoadFile (tclIOUtil.c:2791) > BTW: "make install" fails because of "install-docs" in Makefile, > maybe it would make sense to change the Makefile to be more > aware of missing "dtplite"-missing situations. The idea is that if you are building from a released tarball then the built documentation is included and you don't need dtplite. If you're building direct from the repo, you need dtplite (and autoconf, etc.). > Nice: The ns_thread.test(s) double the memory usage, saturate my box with > 100% CPU load... but, once done, all falls back to where it started. Well at least something's working! ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
