8000 Syft crash [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0x123a0da] · Issue #3872 · anchore/syft · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Syft crash [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0x123a0da] #3872

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.

Sign up for GitHub

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

Jump to bottom
Closed
popey opened this issue May 9, 2025 · 4 comments · 8000 Fixed by #3875
Closed

Syft crash [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0x123a0da] #3872

popey opened this issue May 9, 2025 · 4 comments · Fixed by #3875
Assignees
@wagoodman
Labels
bug Something isn't working

Comments

@popey
Copy link
Contributor
popey commented May 9, 2025

What happened:

I ran Syft with the same options about a thousand times, all successful, then it crashed.

What you expected to happen:

Not crash.

Steps to reproduce the issue:

Run this.

#!/bin/bash

export SYFT_CHECK_FOR_APP_UPDATE=false
export SYFT_LOG_LEVEL=debug
export SYFT_PARALLELISM=64

for container in anchore/test_images:grype-quality-dotnet-69f15d2; do
  sbom=$(echo $container | tr '/' '_' | tr ':' '.')
  for count in {000001..100000}; do
    for arch in amd64 arm64; do
      export SYFT_LOG_FILE="$count"-"$sbom"-"$arch".log
      echo "== Run $count for $container $arch"
      if ! syft "$container" -o syft-json="$count"-"$sbom"-"$arch"-syft.json; then
        echo "Fail"
        exit
      fi
    done
  done
done

Anything else we need to know?:

syft-trace.txt

000517-anchore_test_images.grype-quality-dotnet-69f15d2-arm64.log

Environment:

  • Output of syft version: syft 1.23.1
  • OS (e.g: cat /etc/os-release or similar): Ubuntu 24.04
@popey popey added the bug Something isn't working label May 9, 2025
@wagoodman wagoodman self-assigned this May 9, 2025
@wagoodman wagoodman added this to OSS May 9, 2025
@wagoodman wagoodman moved this to In Progress in OSS May 9, 2025
@willmurphyscode
Copy link
Contributor

I modified the above script to use go run -race ./cmd/syft to see what data races might be present, since a data race is a likely cause of a program that sometimes panics on the same task. It found several - see the attached document.

race-detector.txt

@kzantow
Copy link
Contributor
kzantow commented May 9, 2025

It looks like most of the race issues are from: https://github.com/anchore/syft/blob/main/syft/pkg/cataloger/generic/cataloger.go#L178

@wagoodman
Copy link
Contributor

I've got a fix inbound

@wagoodman wagoodman mentioned this issue May 9, 2025
Merged
4 tasks
@wagoodman wagoodman moved this from In Progress to In Review in OSS May 9, 2025
@github-project-automation github-project-automation bot moved this from In Review to Done in OSS May 9, 2025
@popey
Copy link
Contributor Author
popey commented May 9, 2025

(just noticed a bug in the script. it doesn't tell syft which arch to use) Ahh well, still found the issue :D

@BrewTestBot BrewTestBot mentioned this issue May 14, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wagoodman wagoodman

Labels
bug Something isn't working
Projects
OSS
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: remove race when writing errors in generic cataloger anchore/syft
4 participants
@wagoodman @popey @kzantow @willmurphyscode
0