On Wed, 19 May 2010 15:25:52 PDT ron minnich <[email protected]> wrote: > On Wed, May 19, 2010 at 3:02 PM, Bakul Shah <[email protected]> wrote > : > > >> It gives you the option of not restarting the system call until later. > >> There could be more complex usage scenarios. > > > > I don't understand this. > > You read the "start of the system call" message. The process is > stopped. It has not run the system call. > > You have a lot of options at that point. You could, programatically, > drop the person into acid (the debugger, not the liquid) and, when > they exit, resume the process. You really do have lots of control.
What I don't understand is why do I need these options. I just want tracing. I don't want to do acid (debugger, low pH liquid or LSD)! But never mind. I probably won't get it. Why is the performance so poor? cd ratrace mk clean time ratrace -o /dev/null -c mk # about 19.67 seconds mk clean time mk # about 0.88 seconds And here I thought naming it ratrace would make it go faster. [yes, I added the -o option for precisely this sort of thing)
