Daikon Tracer 2020-09-09

By Max Woerner Chase

I've looked into Daikon's documentation, and Python tracer code, and concluded that I want to write a tracer for Daikon with a minimal/useless feature set, and refine it to gather more data. So, to start with, I just want something that properly sets up a tracer function, and runs code. I've concluded that the best way to accomplish that is to just copy the execfile module from Coverage.py, and probably much of the rest of Coverage.py.

Looking over the source code, I see that my next task is to psych myself up to use optparse in spite of its deprecation. I'm tempted to try and port things to argparse, but I'd need a better understanding of both modules to be able to accomplish it. I can at least recognize the danger here: that there is some subtlety of behavior that is different between the libraries, that would produce mysterious bugs.

I've started working on porting stuff over, but I don't have a good sense of the right order to work on this in, so I just kind of started copying over from the top down. This might be wrong, we'll see.

In any case, in the coming days, I'll work on getting things together enough to set up a stub trace function. For now, I should wrap up.

Good night.