Parent Directory | Revision Log
|Links to HEAD:||(view) (annotate)|
|Links to release-18e:||(view) (annotate)|
When tracing, set the verbosity level of print-frame-call to 1. If you use the *default-print-frame-call-verbosity* variable I committed last week (to get source print along with frames in backtraces) then you would also print the source in trace prints.
From Eric Marsden: fix typos in comments, signal more specific error types, remove some stale code, fix a few compiler warnings in the runtime.
Remove :cgc restriction on *trace-encapsulate-default*
Backout the previous commit, function tracing still doesn't work on a CGC system, noted by Paul.
Function tracing should now work under CGC so it no longer needs to use encapsulation by default.
Only need to default to trace encapsulation with CGC.
Werkowskis source kit 1.03.7
Fix headed boilerplate.
special-form-p -> special-operator-p
Added pretty-printer directives so that arg lists and results print better. [From Rob:] Fixed untrace-1 not to flame out when untracing untraced functions.
Changed to use PRINT-FRAME-CALL instead of the internal PRINT-CALL-FRAME-1.
Substantially rewritten. TRACE has a new syntax. It now subsumes the old encapsulation-based trace via the :ENCAPSULATE option. Interpreted functions and generic functions are traced via encapsulation by default, which works. Conditional stuff works much better.
Fixed to actually allow tracing anonymous function objects. Changed to allow tracing of macros. When tracing an already traced function, untrace and retrace it, instead of ignoring the second request. Moved the undefined error for UNTRACE to the UNTRACE-1 subfunction, instead of signalling it at macroexpand time. In TRACE-1, added an assertion that there isn't already an entry in the trace breakpoint table, since sometimes we seem to be forgetting about breakpoints.
Bind debug:*stack-top-hint* before calling break.
Don't bother warning about dynamic flow of control, because it is obvious from the call depth numbers and the warning can happen at real confusing times.
Made TRACE and UNTRACE handle function objects as well as function names. Made calling UNTRACE while with a BREAK from TRACE'ing work fine. No output occurs at the end of the call even though there was TRACE output at the beginning of the call before going into the BREAK loop.
Changed to use DESTRUCTING-BIND instead of WITH-KEYWORDS, so we get some error checking, and stop using that old crock.
Added CLEAR-TRACE-BREAKPOINT-RECORD to ext:*setf-fdefinition-hook*. Fixed package system, so the old TRACE and new one didn't conflict with variable names. Added debug:*trace-frame* to support users who want to enter expressions for evaluation in the frame. This is described in the TRACE doc string. Fixed TRACE interface to support any function name, not just symbols. Underlying support allowed this, but TRACE complained when it inspected its arguments. Added full support for documented interface of TRACE since before it only allowed users to see arguments and output without conditionalization, printing, etc.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.
|Powered by ViewVC 1.1.5|