github / github/codeql-cli-binaries

Xcode iOS simulator build fails when codeql is injected

Ouverte
#147 14 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
CLI
Langage dominant
Aucune donnée de langage
Étoiles
1k
Forks
184
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

When CodeQL is enabled for our repo here https://github.com/xamarin/ios-sim-sharp, the build crashes, with codeql is on the call stack.

See the attached: [failure.log](https://github.com/github/codeql-cli-binaries/files/10198085/failure.log)

The error below also appears in the log:
```
2022-11-18T14:31:19.4879860Z dyld: dyld cache load error: shared cache file open() failed
2022-11-18T14:31:19.4882650Z dyld: could not load inserted library '/Users/runner/work/_temp/codeql3000/github/codeql/tools/osx64/libtrace.dylib' because no suitable image found. Did find:
2022-11-18T14:31:19.4885600Z /Users/runner/work/_temp/codeql3000/github/codeql/tools/osx64/libtrace.dylib: mach-o, but not built for platform iOS-sim
```

[success.log](https://github.com/github/codeql-cli-binaries/files/10198084/success.log) is the same build, without codeql enabled, so that you can compare.

Also attached is [codeql-init.log](https://github.com/github/codeql-cli-binaries/files/10198083/codeql-init.log), with the output of the CodeQL init task.

I tested with the latest codeql, 2.11.4, and the error still happens.

Thanks for investigating & hopefully fixing or suggesting a workaround.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Start by comparing the attached failure.log and success.log, then review codeql-init.log and the CodeQL injection output for the iOS simulator build. Trace where libtrace.dylib is inserted and verify that the injected library is not loaded into the iOS-sim process; done means the CodeQL-enabled build completes successfully.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
ios
Domaine
build-system, devtools, mobile-dev
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.