Bug#867440: trace-cmd: segfaults while processing certain trace files

[Sebastian Andrzej Siewior]

Package: trace-cmd
Version: 2.6-0.1
Severity: important
Tags: fixed-upstream upstream patch

Hi,

I record a trace with
	trace-cmd start -e sched_switch; sleep 2; trace-cmd stop; trace-cmd extract;

and then dump it and this crashes
	trace-cmd report trace.dat

|  [xhci-hcd:xhci_urb_giveback] bad op token {
|  [xhci-hcd:xhci_urb_enqueue] bad op token {
…
|  [jbd2:jbd2_checkpoint_stats] function jiffies_to_msecs not defined
|  unknown op '->'
|  [i915:i915_va_alloc] unknown op '->'
|  [fs_dax:dax_pmd_insert_mapping_fallback] unknown op '~'
|Segmentation fault

This has been fixed by upstream via
	https://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git/commit/?id=02e85fa19d4aed68d6a3a0cd21b9d4ce1f55025a

and is part of the v2.6.1 release. Please update the package to v2.6.1
for unstable. The commit mentioned above can be cherry-picked on-top of
the v2.6 release. I suggest doing this for the Stretch release.

Sebastian