On MacOS, libtrace.dylib can't load into platform binaries for build instrumentation during DB creation about codeql-cli-binaries

[matt-gretton-dann]

Thank you for your issue report.

Looking at the report above I suggest the following steps:

• Please ensure you are using the latest CodeQL CLI binaries.
• Use an Xcode app with a shorter path. (This needs to be its realpath and not a symlink.

I have successfully done a CodeQL managed build using Xcode installed in /Applications/Xcode.app using latest WebKit.git master and CodeQL CLI Binaries version 2.1.0 with the command line you provided:

codeql database create /tmp/db --language=cpp --command="./Tools/Scripts/build-webkit --jsc-only --debug"

/tmp/db ends up being about 2.8GB in size.

If you have any further questions please feel free to ask.

[xpcmdshell]

Hi, thanks for checking out my issue. I'm still seeing the same errors about libptrace.dylib not being injected into platform binaries. Using Xcode from /Applications doesn't seem to help. What version of MacOS are you using to test this, out of curiosity?

My database after generation for latest commit of webkit is also about 2.8GB, so maybe there's nothing significant missing 🙂

[matt-gretton-dann]

sw_vers reports:

ProductName:    Mac OS X
ProductVersion: 10.15.4
BuildVersion:   19E287

xcodebuild -version reports:

Xcode 11.1
Build version 11A1027

Another thing to try (along with using Xcode in /Applications) is to put the database in /tmp when creating it (the directory can be relocated afterwards).

If that still fails I would appreciate a copy of /log/build-tracer.log and /log/database-create-*.log. These are plain text files, so feel free to examine what they contain before you send them to ensure they have no secrets (via DropBox or equivalent is fine). These may help to diagnose what is happening.

[xpcmdshell]

Same thing with creating the database in /tmp/ 🤔

Here's a copy of my logs, let me know if there's anything else I can provide to be helpful:
https://drive.google.com/open?id=1Gm-lQIV0sNOCt863esjjm6Ayv9rxx2_5

[matt-gretton-dann]

Thank you for these. I have taken local copies - so don't feel the need to preserve them in your Google Drive.

The good news is that from the database create log I think the vast majority of the build is being processed correctly - so the database should be usable.

Unfortunately I don't have a solution to the problem you've been having yet. I need to do some further investigations locally, and this will take some time.

[xpcmdshell]

Sounds good, thanks for taking a look into this

[Manouchehri]

Any update on this?

[hmakholm]

Much code regarding build instrumentation on MacOS has changed recently as part of getting tracing on M1 to work. Is this issue still live?