| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
tcltest 2.5, since we never test with earlier tcltest versions
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
string of the corresponding codePtr->source.
|
|
|
|
| |
the length to a non-positive value so nothing tries to read offsets from
a NULL pointer.
|
|
|
|
| |
combination with tcltest86.dll to do that (Windows only)
|
|\
| |
| | |
cause more harm than good. Purged them (except in zlib files).
|
| |\
| | |
| | | |
more harm than good. Purged them.
|
| | |
| | |
| | | |
more harm than good. Purged them.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* generic/tclProc.c: when compiling a proc survives too long. We
* tests/execute.test: only need it there long enough for the right
TclInitCompileEnv() call to re-stash it into envPtr->procPtr. Once
that is done, the CompileEnv controls. If we let the value of
iPtr->compiledProcPtr linger, though, then any other bytecode compile
operation that takes place will also have its CompileEnv initialized
with it, and that's not correct. The value is meant to control the
compile of the proc body only, not other compile tasks that happen
along. Thanks to Carlos Tasada for discovering and reporting the
problem. [Bug 2802881].
|
| | | |
|
| | |
| | |
| | |
| | | |
bytecode is invalidates in the right situations.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* tests/autoMkindex.test: revealed by -singleproc 1 -debug 1
* tests/exec.test: options to make test.
* tests/execute.test:
* tests/interp.test:
* tests/io.test:
* tests/namespace.test:
* tests/regexpComp.test:
* tests/stringComp.test:
* tests/unixInit.test:
* tests/winPipe.test:
|
| | |
| | |
| | |
| | |
| | | |
protect all calls that may cause traces on ::errorInfo or
::errorCode to corrupt the stack [Bug 804681]
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* generic/tclProc.c: when compiling a proc survives too long. We
* tests/execute.test: only need it there long enough for the right
TclInitCompileEnv() call to re-stash it into envPtr->procPtr. Once
that is done, the CompileEnv controls. If we let the value of
iPtr->compiledProcPtr linger, though, then any other bytecode compile
operation that takes place will also have its CompileEnv initialized
with it, and that's not correct. The value is meant to control the
compile of the proc body only, not other compile tasks that happen
along. Thanks to Carlos Tasada for discovering and reporting the
problem. [Bug 2802881].
|
| | |
| | |
| | |
| | |
| | |
| | | |
* tests/execute.test: stack trace when a compile epoch bump triggers
fallback to direct evaluation of commands in a compiled script.
[Bug 2037338]
|
| | |
| | |
| | |
| | | |
fails (with a crash) in an unfixed memdebug build on 64-bit systems.
|
| | |
| | |
| | |
| | | |
test causes a mem failure.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
manifestations in the future. Add tcltest support for finalization.
|
| | |
| | |
| | |
| | | |
Correct duplicate test names.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* generic/tclProc.c: when compiling a proc survives too long. We
* tests/execute.test: only need it there long enough for the right
TclInitCompileEnv() call to re-stash it into envPtr->procPtr. Once
that is done, the CompileEnv controls. If we let the value of
iPtr->compiledProcPtr linger, though, then any other bytecode compile
operation that takes place will also have its CompileEnv initialized
with it, and that's not correct. The value is meant to control the
compile of the proc body only, not other compile tasks that happen
along. Thanks to Carlos Tasada for discovering and reporting the
problem. [Bug 2802881].
|
| | | |
|
| | |
| | |
| | |
| | | |
* tests/execute.test:
|
|/ /
| |
| |
| |
| |
| | |
* tests/execute.test: stack trace when a compile epoch bump triggers
fallback to direct evaluation of commands in a compiled script.
[Bug 2037338]
|
| |
| |
| |
| | |
script bytecode is invalidated in the right situations.
|
| |
| |
| |
| | |
script bytecode is invalidated in the right situations.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* doc/fconfigure.n, doc/interp.n, doc/unknown.n:
* library/auto.tcl, library/init.tcl, library/package.tcl:
* library/safe.tcl, library/tm.tcl, library/msgcat/msgcat.tcl:
* tests/all.tcl, tests/basic.test, tests/cmdInfo.test:
* tests/compile.test, tests/encoding.test, tests/execute.test:
* tests/fCmd.test, tests/http.test, tests/init.test:
* tests/interp.test, tests/io.test, tests/ioUtil.test:
* tests/iogt.test, tests/namespace-old.test, tests/namespace.test:
* tests/parse.test, tests/pkg.test, tests/pkgMkIndex.test:
* tests/proc.test, tests/reg.test, tests/trace.test:
* tests/upvar.test, tests/winConsole.test, tests/winFCmd.test:
* tools/tclZIC.tcl:
* generic/tclParse.c (Tcl_ParseCommand): Replace {expand} with {*}
officially (TIP #293). Leave -DALLOW_EXPAND=0|1 option to keep
{expand} syntax for transition users. [Bug 1589629]
|
| |
| |
| |
| | |
* tests/execute.test (execute-9.1): dgp's fix for [Bug 1522803].
|
| |
| |
| |
| |
| | |
Consistent method of calling test constraints, and (try to) move constraint
setup to the top of the test file
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* tests/execute.test: due to addition of bignums.
* tests/expr-old.test:
* tests/expr.test:
* tests/parseExpr.test:
* tests/platform.test:
* tests/string.test:
|
| | |
|
| |
| |
| |
| | |
work and fix.
|
| |
| |
| |
| |
| | |
set on ::errorInfo . When left in place, that trace can cause
later tests to fail.
|
| |
| |
| |
| | |
is limited system stack space (threads-enabled).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* doc/Tcl.n: of the new leading {expand} syntax on words.
* generic/tcl.h: Parses such words as the new Tcl_Token type
* generic/tclBasic.c: TCL_TOKEN_EXPAND_WORD. Updated Tcl_EvalEx
* generic/tclCompile.c: and the bytecode compiler/execution engine
* generic/tclCompile.h: to recognize the new token type. New opcodes
* generic/tclExecute.c: INST_LIST_VERIFY and INST_INVOKE_EXP and a new
* generic/tclParse.c: operand type OPERAND_ULIST1 are defined. Docs
* generic/tclTest.c: and tests are included.
* tests/basic.test:
* tests/compile.test:
* tests/parse.test:
* library/auto.tcl: Replaced several [eval]s used to perform
* library/package.tcl: argument expansion with the new syntax.
* library/safe.tcl: In the test files lindex.test and lset.test,
* tests/cmdInfo.test: replaced use of [eval] to force direct
* tests/encoding.test: string evaluation with use of [testevalex]
* tests/execute.test: which more directly and robustly serves the
* tests/fCmd.test: same purpose.
* tests/http.test:
* tests/init.test:
* tests/interp.test:
* tests/io.test:
* tests/ioUtil.test:
* tests/iogt.test:
* tests/lindex.test:
* tests/lset.test:
* tests/namespace-old.test:
* tests/namespace.test:
* tests/pkg.test:
* tests/pkgMkIndex.test:
* tests/proc.test:
* tests/reg.test:
* tests/trace.test:
* tests/upvar.test:
* tests/winConsole.test:
* tests/winFCmd.test:
|
| | |
|
|/
|
|
|
|
| |
calls that may cause traces on ::errorInfo or ::errorCode to corrupt the stack [Bug 804681]
----------------------------------------------------------------------
|
|
|
|
| |
leak warning by valgrind.
|
|
|
|
|
|
|
|
|
| |
variable "range" [Bug 664743]
* generic/tclExecute.c (ExprSrandFunc): remove unused
variable "result" [Bug 664743]
* generic/tclStringObj.c (UpdateStringOfString): remove unused
variable "length" [Bug 664751]
* tests/execute.test (execute-7.30): fix for [Bug 664775]
|
|
|
|
|
|
|
| |
with options -constraints knownBug -limitConstraints 1 only tests
the knownBug tests. Mostly involves replacing direct access to the
testConstraints array with calls to the testConstraint command
(which requires tcltest version 2).
|
|
|
|
|
| |
This version builds clean on Solaris/SPARC, with GCC and CC, both with and
without threads and both in 32-bit and 64-bit mode.
|