[SRU] segfaults with certain trace.dat files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kernelshark (Debian) |
Fix Released
|
Unknown
|
|||
kernelshark (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lunar |
Fix Released
|
Undecided
|
Unassigned | ||
Mantic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[ 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:/
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.
Changed in kernelshark (Ubuntu): | |
status: | New → Fix Released |
Changed in kernelshark (Ubuntu Mantic): | |
status: | New → Fix Released |
Changed in kernelshark (Ubuntu Lunar): | |
status: | New → Triaged |
Changed in kernelshark (Debian): | |
status: | Unknown → Fix Released |
summary: |
- segfaults with certain trace.dat files + [SRU] segfaults with certain trace.dat files |
tags: |
added: verification-done-lunar removed: verification-needed-lunar |
debdiff attached.