Multiple Trace Output

[gordonguthrie]

I have multiple traces attached - I fire and event and get a trace - but I can't easily tell which trace triggered it - multiple arity fns with records in each argument are hard to mentally parse to reconstruct the arity of the call in your head

[andytill]

I could easily allow searches on module:fun/arity string, you can now even see multiple functions with by using a pipe i.e. func1|func2.

A better but more involved way might be to spawn a separate window that only shows traces for that function, like WireSharks TCP follow stream.

I don't want to add more colours since it is not searchable and colours already denote trace log states. What were your thoughts?

[andytill]

I have since needed this myself!

The easy answer is to spawn another window that contains the trace list and filter field, and populate the filter with the function name e.g. gen_server:call/3 which will only show the traces for that function, steps:

• Add a context menu item to the right click menu
• When the item is executed create a new window and pass in the function name string and DbgTraceView.sortedTtraces. The control in the window should create its own filtered version of the list so changes to the filter will only affect its own view.
• Set the filter string in the filter field.