FS#76170 - [trace-cmd] kernelshark does not start (symbol lookup error in /usr/lib/libtracecmd.so.1)
Attached to Project:
Community Packages
Opened by Claudio Cabral (claudiocabral) - Tuesday, 11 October 2022, 10:52 GMT
Last edited by David Runge (dvzrv) - Wednesday, 16 November 2022, 23:21 GMT
Opened by Claudio Cabral (claudiocabral) - Tuesday, 11 October 2022, 10:52 GMT
Last edited by David Runge (dvzrv) - Wednesday, 16 November 2022, 23:21 GMT
|
Details
Description:
kernelshark does not start because of a symbol lookup error in libtracecmd.so.1: kernelshark: symbol lookup error: /usr/lib/libtracecmd.so.1: undefined symbol: tracecmd_get_file_state Reverting to trace-cmd to version 3.1.1-1 fixes the issue Additional info: * package version(s) kernelshark 2.1.1-1 trace-cmd 3.1.2-1 Steps to reproduce: launch kernelshark from the command line to observe the error |
This task depends upon
Closed by David Runge (dvzrv)
Wednesday, 16 November 2022, 23:21 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with trace-cmd 3.1.4-1 and kernelshark 2.1.1-2
Wednesday, 16 November 2022, 23:21 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with trace-cmd 3.1.4-1 and kernelshark 2.1.1-2
Will look into it. As there has been no soname change, I assume that upstream just broke this...
Quality!
this bug has been going on for a couple of months, I confess I was too lazy to report it earlier
thinking "surely someone else uses kernelshark and arch linux"
The test suite now requires root as it uses /sys/kernel/tracing.
> kernelshark build neither against 3.1.2 nor against 3.1.4
If trace-cmd 3.1.4 is built with !lto, kernelshark can be rebuilt. I don't understand it, though.