Skip to content

LD_PRELOADing ldlogger fails when CodeChecker is not installed system wide #4474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nuudlman opened this issue Feb 28, 2025 · 1 comment
Open

Comments

@nuudlman
Copy link

Describe the bug
LD_PRELOAD is set to just ldlogger.so, which requires ldlogger.so to be installed systemwide. If you have CodeChecker installed with something like uv, this fails. If the LD_PRELOAD is changed to an absolute or relative path to the installation, it should be fixed.

CodeChecker version

[INFO 2025-02-28 08:56] - CodeChecker analyzer version:

Kind Version
Base package version 6.24.4
Package build date 2024-10-28T15:46
Git commit ID (hash) 454d978
Git tag information 6.24.4

[INFO 2025-02-28 08:56] - CodeChecker web version:

Kind Version
Base package version 6.24.4
Package build date 2024-10-28T15:46
Git commit ID (hash) 454d978
Git tag information 6.24.4
Server supported Thrift API version 6.58
Client Thrift API version 6.58

To Reproduce
Steps to reproduce the behaviour:

  1. Install CodeChecker with uv: uvx CodeChecker
  2. Attempt to intercept compile_commands.json: uvx CodeChecker log -b make -o compile_commands.json
  3. Get many LD_PRELOAD errors:
    ERROR: ld.so: object 'ldlogger.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

Expected behaviour
LD_PRELOAD doesn't error out and capturing compile_commands.json works

Desktop (please complete the following information)

  • OS: Arch Linux (linux 6.13)
  • Browser: Firefox
  • Version: 136.0b9

Additional context
Add any other context about the problem.

@bruntib
Copy link
Contributor

bruntib commented Feb 28, 2025

Please, check if the master version (or 6.25.0-rc1) fixes this issue. This PR is supposed to solve it: #4394.
Thank you!

@bruntib bruntib closed this as completed Feb 28, 2025
@bruntib bruntib reopened this Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants