On Wed, Oct 28, 2020 at 1:13 AM David Marchand <david.march...@redhat.com> wrote: > > On Fri, Oct 23, 2020 at 10:01 AM David Marchand > <david.march...@redhat.com> wrote: > > > > Following recent increase of an internal array that was limiting CTF event > > descriptions, I had a second look at the code. > > All of this is slow path, so I see no reason in keeping this limitation > > and we can go with dynamic allocations. > > > > While at it, I tweaked the metadata file output. > > > > I consider this -rc2 material. > > Comments? > Thanks.
The Generated metadata has issues. Please check Reproducer: echo "trace_autotest" | ./build/app/test/dpdk-test -c 0x3 --trace=.* --no-huge --trace=.* [main][dpdk.org] $ babeltrace /home/jerin/dpdk-traces/rte-2020-10-28-PM-02-02-37/ [error] at line 1303: invalid character '0x11' [error] at line 1303: token "": syntax error, unexpected ERROR [error] Error creating AST [warning] Unable to open trace metadata for path "/home/jerin/dpdk-traces/rte-2020-10-28-PM-02-02-37". [warning] [Context] Cannot open_trace of format ctf at path /home/jerin/dpdk-traces/rte-2020-10-28-PM-02-02-37. [warning] [Context] cannot open trace "/home/jerin/dpdk-traces/rte-2020-10-28-PM-02-02-37" from /home/jerin/dpdk-traces/rte-2020-10-28-PM-02-02-37/ for reading. [error] Cannot open any trace for reading. [error] opening trace "/home/jerin/dpdk-traces/rte-2020-10-28-PM-02-02-37/" for reading. [error] none of the specified trace paths could be opened. > > -- > David Marchand >
