SBCL Internals The pages on this CLiki-driven site can be edited by anybody at any time. No warranty of any kind can therefore be made; any implied warranties of merchantability or fitness for a particular purpose are expressly disclaimed

TRACE

TRACE has two parallel mechanisms: encapsulation? and breakpoint? based. Both work less-then perfectly, and interact with PROFILE? and CLOS? in various nasty ways.

Vague plans

Nikodemus' plan of attack:

• Throw away the current encapsulation machinery, and write breakpoint based Fwrapper implementation that DTRT on anonymous functions as well.

• Rewrite TRACE in terms of FWRAP and friends: this means that there would be only one mechanism to worry about, which should correspondingly get more care and attention.

• At this point only FWRAP should be relying on breakpoints, so it would be time to audit the breakpoint code and get rid of the stale stuff.

• If it turns out that having breakpoint based FWRAP is not feasible -- think again.

Possible extensions and interface changes

• Rename :WHEREIN :INSIDE.

• Add :OUTSIDE. (Complement of :INSIDE.)

• Add :IN. (Like :INSIDE, but only for the previous frame.)

• Add :STEP. (Enable stepping for the traced function.)

This page is linked from: Fwrapper   One Point Zero  

CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively