Hi, Libor... You did everything right... On Wed, 10 Mar 2021, Libor Pechacek wrote:
$ gcc -Wl,-rpath,. -L. -o main main.c -lworkload
^ ^ ... it is very unfortunate that you hit a usability bug. It would have worked if you had used $PWD instead of '.', such as: $ gcc -Wl,-rpath,$PWD -L$PWD -o main main.c -lworkload Libpulp, more specifically ulp_trigger, currently ignores things that don't start with a foward slash. This is where it happens: https://github.com/SUSE/libpulp/blob/master/tools/introspection.c#L384-L385 These lines should probably just go away (probably no side-effects).
What am I doing wrong, apart from the uneducated approach, that ulp_trigger complaints about the missing libworkload.so?
Nothing wrong. I'm sorry you hit this bug.
Side notes: - It is unclear how to build live patches. README.md contains the high-level overview but not concrete steps or a pointer to a "how to". - ulp_packer help is wrong. It says "packer <descr> <.so> [.ulp]" while it's now "packer <descr> <.ulp>" - The role of ulp_post is unclear in the process. There is a clue in the commit log that introduces it but it was beyong my current knowledge level. - I've inferred compiler parameters and command usage from what I saw in "make check" output. - ulp_trigger says nothing in case libpulp.so is not preloaded. I suggest that it prints some diagnostic message.
Thank you so much for this feedback! Cheers, Gabrie