summaryrefslogtreecommitdiffstats
path: root/generic/tclTrace.c
Commit message (Collapse)AuthorAgeFilesLines
* TIP#207 IMPLEMENTATIONdgp2004-08-021-2/+2
| | | | | | | | | | * doc/interp.n: Added support for a -namespace option to the * generic/tclBasic.c: [interp invokehidden] command. Also added an * generic/tclInt.h: internal routine TclObjInvokeNamespace() and * generic/tclInterp.c: corrected the flag names TCL_FIND_ONLY_NS and * generic/tclNamesp.c: TCL_CREATE_NS_IF_UNKNOWN that are passed to the * generic/tclTrace.c: internal routine TclGetNamespaceForQualName(). * tests/interp.test: [Patch 981841]
* TIP#143 implementation; still needs docs and more tests...dkf2004-05-131-4/+7
|
* * generic/tclTrace.c (TclCheckInterpTraces): The TIP 62dgp2004-03-011-2/+2
| | | | | | | | * generic/tclTest.c (TestcmdtraceCmd): implementation introduced a * tests/trace.test (trace-29.10): bug by testing the CallFrame level instead of the iPtr->numLevels level when deciding what traces created by Tcl_Create(Obj)Trace to call. Added test to expose the error, and made fix. [Request 462580]
* * generic/tclTrace.c (TclTraceExecutionObjCmd)hobbs2004-02-171-6/+4
| | | | (TclTraceCommandObjCmd): fix possible mem leak in trace info.
* All uses of 'panic' (the macro) changeddavygrvy2003-12-241-4/+4
| | | | | | | to 'Tcl_Panic' (the function). The #define of panic in tcl.h clearly states it is deprecated in the comments. [Patch 865264]
* * generic/tclBasic.c: Fixed error in ref count management of commanddgp2003-10-031-7/+28
| | | | | * generic/tclCmdMZ.c: and execution traces that caused access to freed memory in trace-32.1. [Bug 811483].
* * generic/tclTrace.c: Corrected comingling of introspection results ofdgp2003-10-021-1/+17
| | | | | [trace info command] and [trace info execution]. [Bug 807243] Thanks to Mark Saye.
* Removed trivially-unreachable line [Bug 771939]dkf2003-07-161-2/+1
|
* Win compilation fixvincentdarley2003-07-021-2/+2
|
* More trace factoring - variable traces are the target this time.dkf2003-06-261-2/+678
|
* Factored out the trace code - it's big enough to be its own maintenance areadkf2003-06-251-0/+2299
and tricky enough to discourage non-specialists...