-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix panic scanning binaries without symtab #2736
Comments
Hi @rplessl, thank you for the report. I am trying to reproduce this in my environment (MacOS) and failing. I've tried setting up a go.mod to include just the package referenced in the error message and I've also tried scanning just the offending binary (clang-386-darwin.obj) separately, but I can't get the same crash. Do you by chance have a public container that we could look at to reproduce? Alternatively would you be able to run this scan on a different system to see if it reproduces there, too? Thanks! |
Hi @tgerla! It was not so easy to reproduce this image with public images, but I get a dockerfile snippet with exactly the same behavior. In our pipeline we are running linux/amd64 (and locally myself Docker Desktop on an arm mac using the virtualization not resetta). With the Dockerfile
I will get the same error with syft 1.1.0 (but not on syft 1.0.1):
I have created the docker container locally using the Dockerfile above and
(If I remove the installation of gocover-cobertura, the symptom disappears ... but is another vector of solution besides my syft problem) |
What happened:
The newest version of syft 1.1.0 has a invalid memory address or nil pointer reference, in the version v1.0.1 this was not part of our execution path.
What you expected to happen:
Steps to reproduce the issue:
see above
Anything else we need to know?:
Environment:
syft version
:cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: