should drmgr also split trace event into phases and order it?

_From [bruen...@google.com](https://code.google.com/u/109494838902877177630/) on November 18, 2013 13:42:43_

Today drmgr only separates the bb event into phases.
For traces, drmgr can still be used the bb event's for_trace parameter.
But the trace event itself is unordered and unsplit.
So far no libs or tools that use the trace event have needed central mediation.

With the for_trace param to the bb event, instru is already present, so app2app and
analysis phases don't make much sense for traces. So we're really talking
about single-instr insertion, and priority ordering.

Should we consider the trace event to be for advanced users, and have
others use the for_trace bb event instead? Should we change the inc2add
sample to use bb event w/ for_trace==true?

_Original issue: http://code.google.com/p/dynamorio/issues/detail?id=1323_