-
I committed my one-line fix for generic/tclXprofile.c into HEAD.
The problem with profiling under Tcl-8.6 (still seen under 8.6b1) appears to be of Tcl's own doing... See, for example:
https://sourceforge.net/tracker/index.php?func=detail&aid=2017162&group_id=10894&atid=110894.
2009-10-13 22:55:25 UTC in Extended Tcl (TclX)
-
The profile-crash is now fixed. Use the patch attached to artifact 1925400:
https://sourceforge.net/tracker/index.php?func=detail&aid=1925400&group_id=13247&atid=113247
Other self-tests break mostly because the core Tcl changed wordings of its error messages...
2009-10-13 22:51:00 UTC in Extended Tcl (TclX)
-
When I compile TclX (from head) against Tcl-8.6b1 and attempt to run TclX' own self-tests, the profile test inevitably crashes inside PushProcCallFrame:
#0 0x08089368 in PushProcCallFrame (clientData=0x96b0f90, interp=0x95c7f90,
objc=1, objv=0x95caa70, isLambda=0)
at /data/mteterin/tcl8.6b1/generic/tclProc.c:1573
#1 0x08089560 in TclNRInterpProc (clientData=0x96b0f90...
2009-10-13 21:41:01 UTC in Tcl
-
kot committed patchset 1800 of module tclx to the Extended Tcl (TclX) CVS repository, changing 1 files.
2009-10-13 19:28:23 UTC in Extended Tcl (TclX)
-
As the originator, I certainly think, this would be quite useful. Unfortunately, I no longer work for a client, where I saw this situation a couple of times per week...
2009-08-07 16:55:36 UTC in jTDS - SQL Server and Sybase JDBC driver
-
I would not be at all surprised, that 8.6 is causing a problem. Especially, 8.6 /beta/ :-) Please, check with 8.5 (you don't need Tcl's libraries recompiled and can use the production binaries). Thanks!
2009-07-31 16:58:45 UTC in Extended Tcl (TclX)
-
You are right -- you are doing 32-bit. I was looking at the originator's message initially and noticed the wide pointers.
I'm puzzled, why you are seeing crashes and I don't even see a valgrind warning here -- the tests completes cleanly on both Linux/x86 and FreeBSD/amd64 after my patch.
Maybe, we are using a different Tcl? I use tcl-8.5.5, what's yours?.
2009-07-31 15:56:21 UTC in Extended Tcl (TclX)
-
Strange... I just checked the profile.test on Linux -- under valgrind -- and there were no errors... It looks like your Solaris is 64-bit... Maybe, it is that? There are patches in FreeBSD port, that address /some/ 64-bit issues:
Try applying what's under http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/tclX/files/ and check again... Thanks!
2009-07-31 14:51:09 UTC in Extended Tcl (TclX)
-
The crash happens in InitializeProcStack(), when it tries to access framePtr->objv[0] -- with the objv being NULL. The following patch fixes the problem -- and the profile.test passes:
--- generic/tclXprofile.c 2004-11-22 19:12:54.000000000 -0500
+++ generic/tclXprofile.c 2009-07-31 02:44:11.000000000 -0400
@@ -674,5 +674,5 @@
CallFrame *framePtr;
{
- if (framePtr == NULL...
2009-07-31 06:51:57 UTC in Extended Tcl (TclX)
-
In our case, this was a not-so-ancient MS SQL-Server database server. The failing statements were, believe it or not, SELECT queries...
Perhaps, the initial implementation of this feature can just limit itself to such transactions throwing some sort of "unimplemented" exception if anybody wanted to do it to batches or other things, that require the kind of state-keeping you describe in item 2...
2009-07-25 08:40:15 UTC in jTDS - SQL Server and Sybase JDBC driver
