[Bug 2042720] [NEW] [SRU] segfaults with certain trace.dat files

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Sudip Mukherjee (sudipmuk):

[ Impact ]

KernelShark crashes when opening `trace.dat` of 'all events' and can be
used by the user to analyze the particular trace file resulting in a
segfault.

[ Test Plan ]

Grab the trace.dat file from https://bugzilla.kernel.org/show_bug.cgi?id=217429 and save it to $HOME.
Execute kernelshark from terminal by giving the command `kernelshark` and you can see segfault.

With the fix kernelshark will start the gui and load the trace file.

[ Where problems could occur ]

As the fix is in the error path and is only checking for seq.len which
will return if its `0`. It does not change any other code and so does
not change the behaviour so has little chance of regressing the user
behaviour.


[ Other Info ]
 
 The problem exists in 2.2.0, and has been fixed by upstream on 2.2.1. It has been updated on Ubuntu Noble and Mantic. But Lunar still has the problem.
 The diff between v2.2.0..v2.2.1 are only two bugfixes. And one of them fixes the observed segmentation fault.

** Affects: kernelshark (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: kernelshark (Ubuntu Lunar)
     Importance: Undecided
         Status: Triaged

** Affects: kernelshark (Ubuntu Mantic)
     Importance: Undecided
         Status: Fix Released

** Affects: kernelshark (Debian)
     Importance: Unknown
         Status: Fix Released

-- 
[SRU] segfaults with certain trace.dat files
https://bugs.launchpad.net/bugs/2042720
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.