Re: CSV output

[Julia Lawall <julia.lawall@inria.fr>]

[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]



On Wed, 15 Mar 2023, Alexander Aring wrote:

> Hi,
>
> On Mon, Mar 13, 2023 at 2:26 PM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > On Mon, 13 Mar 2023 18:59:50 +0100 (CET)
> > Julia Lawall <julia.lawall@inria.fr> wrote:
> >
> > > > Better yet, I'm hoping to get some time to finish looking at the python
> > > > updates that were sent to me, and where it could be possible to just allow
> > > > you to override the output with a python script.
> > >
> > > OK, no hurry.  I looked into the plugins, but they seem to control only
> > > part of the output and it seems that one would be needed for every type of
> > > event.  I could try writing python, if there is an example.
> >
> > The python plugins are currently broken, and we started adding more
> > features to the plugins to control the output a bit more.
>
> what about the python bindings (under trace-cmd/python/) to parse
> trace files and using the python csv module? I guess the python

What do you mean by parse?  My only goal is to reduce running time, so
parsing the existing output to produce a csv file won't be a benefit.

thanks,
julia

> bindings are something different than the python plugins and they are
> still working?
>
> - Alex
>
>