Possible glibc issue on x86_64 linux systems
Shows how to fix possible glibc issue on x86_64 linux systems. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Bearer segfaulting on x86_64 Linux was fixed in Bearer 1.4.0. If the scanner crashes with segfaults on Linux, upgrade to 1.4.0 or later and confirm the crashes are gone.
Steps
- Bearer segfaulting on x86_64 Linux was fixed in Bearer 1.4.0.
- If the scanner crashes with segfaults on Linux, upgrade to 1.4.0 or later and confirm the crashes are gone.
When to use
You are seeing this: Issue Bearer/bearer#899 (closed, 8 comments): [!--- Provide a general summary of the issue in the Title above --] ## Description Currently on linux it looks like we are seeing some segfaults with some users that have the x86\64 instruction set. Use this skill when you run into "Possible glibc issue on x8664 linux systems".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: hostname 5.10.0-21, Debian 5.10.162-1, Bearer 1.4.0. If you are on something much newer or older, the details may have shifted.
Why this happens
Issue Bearer/bearer#899 (closed, 8 comments): [!--- Provide a general summary of the issue in the Title above --] ## Description Currently on linux it looks like we are seeing some segfaults with some users that have the x86\_64 instruction set.
Sources
- https://github.com/Bearer/bearer/blob/main/.goreleaser/common.yaml#L52-L56
- https://github.com/Bearer/bearer/issues/899
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.